Every time I install a game, or even OpenOffice, part of the installation routine is installing yet another Visual C++ 2005/2008 redistributable, right next to the 10 others I already have on my system.
Why are so many different versions (of what feels like the same thing) necessary?
Visual C++ redistributables are components shipped by app developers who use Visual C++ to write their software. By using Microsoft's well-tested and widely used code inside their apps, developers save their development cost by avoid writing commonly-used code (e.g. sin and cos math functions and handling of common user interface elements like textbox or button). Due to fragmentation in the runtime versions used by the app developers, you would see a long list of Visual C++ redistributables if you install a lot of apps. Uninstalling one Visual C++ redistributable could save you a few megabytes of disk space, but you risk breaking some apps in doing so.
Because programmers rely on Microsoft to keep the Visual C++ runtime up to date, Microsoft releases security update for the redistributables, but due to programmer demands, Visual C++ redistributables do not supersede each other and old versions are kept for compatibility. Some apps are very specific about the version of the Visual C++ dlls they require to make sure the app runs exactly as published. Their authors hold on updating to the latest runtime until they tested their app's compatibility with the new runtime. It is one way to prevent a few thousands calls from angry customers after Microsoft releases an update to the redistributable. Most apps, however, bind to the latest edition of the same major version, as it is the default behavior and the benefit from immediate and effortless security updates outweighs risks in breaking changes delivered by redistributable updates.
Microsoft also has to support a lot of Visual C++ runtimes because it has no idea which one the app developer would choose. Multiple versions of Visual C++ redistributables can be required even within the same app, for example, if an app depending on Visual C++ 2008 redistributable uses a component depending on Visual C++ 2005 redistributable, the app's developer must ship both versions of Visual C++ redistributables. On a 64 bit computer, the system could have both x86 and x64 editions of Visual C++ Redistributables installed, since Visual C++ redistributable is a commonly used component, and it is normal to have both 32bit apps and 64 bit apps (or even apps that contains both 32 bit code and 64 bit code) installed on a 64 bit system.
You can probably find the app installing a redistributable by looking for an app with the same install date as the redistributable, but there is no telling how many other apps with a later install date are depending on the same redistributable. The amount of time you spend on finding the exact dependency would most likely not worth the few megabytes you may save by uninstalling the redistributables.
The reason is that they are not same thing. First you need to understand that every version of MSVC++ ships with its own version of runtime libraries. There are also 32 and 64 bit versions. Also, there are service packs bring updated versions of runtime libraries.
If you do have 10 installations, can you list their names? I don't think that you should have more than 4 (32 and 64 bit for 2005 and same for 2008). Service packs should replace unupdated versions.
There are many versions of the C++ redistributable files, unless you know precisely which program will use the file, remove even one a and every program that used it will disable permanently unless re-installed.
Those who have many programs installed will have many versions of them. Microsoft allows it to be redistributed, so rather than invent new code each time, a developer can just pop one of those in for you.
They are tiny and not big enough to worry about. Many of them are only KB, a few are MB, and better than programs that are a GB.
I know it is aggrivating to see many of them there (I have 21 of them), but leave them alone, your programs will shut down if you remove them. It would also be nice if program developers also labeled them for the individual program, but if they did you would have hundreds more. Right now programs piggyback off them, which enables programs to use coding from both old and new.
I have a degree in computer networking. I wouldn't tell you anything to do to your computer that I wouldn't do to my own
