VC++ Runtime Library not up to date
Posted: Fri Jul 16, 2010 10:11 am
This is more of a gripe than a question, but here goes.
Why is it that nearly a year after Microsoft released VC8 redistributable version 8.0.50727.4053, IA 9 R2 still detects and installs the wrong version that is 3 years out of date? This has cost me (and our customers) untold wasted time because my executables are bound to this version and will not run without it. And every time I install an upgrade to IA, it uninstalls the entire product, reinstalls it, and in the process messes this up again so that I have to remember to go fix it again. And yes, I have my own version of the runtime library detect script in my project, so at least that still works right - even though it ends up installing the wrong version. If I can't rely on my installer tool to have up-to-date runtimes, what good is that feature? For now I guess I'll just take care of this myself by detecting the version and running the vcredist_8_x86.exe myself.
End of gripe.
If there's a better solution to this that doesn't involve me remembering to check these runtimes every time IA is updated, I'm all ears.
Why is it that nearly a year after Microsoft released VC8 redistributable version 8.0.50727.4053, IA 9 R2 still detects and installs the wrong version that is 3 years out of date? This has cost me (and our customers) untold wasted time because my executables are bound to this version and will not run without it. And every time I install an upgrade to IA, it uninstalls the entire product, reinstalls it, and in the process messes this up again so that I have to remember to go fix it again. And yes, I have my own version of the runtime library detect script in my project, so at least that still works right - even though it ends up installing the wrong version. If I can't rely on my installer tool to have up-to-date runtimes, what good is that feature? For now I guess I'll just take care of this myself by detecting the version and running the vcredist_8_x86.exe myself.
End of gripe.
If there's a better solution to this that doesn't involve me remembering to check these runtimes every time IA is updated, I'm all ears.