Discussion:
C++ Redistributables
(too old to reply)
Squeezy99
2010-02-28 11:25:35 UTC
Permalink
Hi,

I am running XP 64 and have been cleaning out some old software etc. I have
many (8) different C++ redistributables listed - do I need all these or
should a new version clean out the old when installed?
Thanks in advance,
Dave
Tim Roberts
2010-03-01 01:46:13 UTC
Permalink
Post by Squeezy99
I am running XP 64 and have been cleaning out some old software etc. I have
many (8) different C++ redistributables listed - do I need all these or
should a new version clean out the old when installed?
As with many things, it depends. If you always rebuild your applications
with the newest compiler, then you don't need the older redistributables.
However, many people want the ability to recompile their old apps and then
release them with the original redistributables.
--
Tim Roberts, ***@probo.com
Providenza & Boekelheide, Inc.
Squeezy99
2010-03-01 16:03:35 UTC
Permalink
Post by Tim Roberts
Post by Squeezy99
I am running XP 64 and have been cleaning out some old software etc. I have
many (8) different C++ redistributables listed - do I need all these or
should a new version clean out the old when installed?
As with many things, it depends. If you always rebuild your applications
with the newest compiler, then you don't need the older redistributables.
However, many people want the ability to recompile their old apps and then
release them with the original redistributables.
--
Providenza & Boekelheide, Inc.
Thanks for the reply.
So a later version of the redist. does not replace an older version, they
are not 'backwards compatible'.

Regards,
Dave
Tim Roberts
2010-03-03 05:34:13 UTC
Permalink
Post by Squeezy99
So a later version of the redist. does not replace an older version, they
are not 'backwards compatible'.
Well, again, the answer is complicated. It would be extremely rare for an
upgrade of a run-time library to make a breaking change. However, thanks
to manifests, unless you take steps to provide otherwise, C executables now
tend to be tightly coupled to one particular version of the run-time
library. Not because they NEED to, but because that's what the default
configuration provides.

Microsoft aims the releases at companys who "certify" their applications
with a particular CRT version, and do not want automatic updates.
--
Tim Roberts, ***@probo.com
Providenza & Boekelheide, Inc.
Loading...