Note the Can you run it? app linked from the system requirements pages provides lots of useful information, but it only checks for. NET and (for desktop) Visual C++ Redistributable runtime. I have a degree in computer networking.ArcGIS Desktop and Pro have system requirements with Windows, specifically. Right now programs piggyback off them, which enables programs to use coding from both old and new. It would also be nice if program developers also labeled them for the individual program, but if they did you would have hundreds more. 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. Many of them are only KB, a few are MB, and better than programs that are a GB. They are tiny and not big enough to worry about. 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. Those who have many programs installed will have many versions of them. 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. 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. 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. On a 64 bit computer, the system could have both x86 and 圆4 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. 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. Microsoft also has to support a lot of Visual C++ runtimes because it has no idea which one the app developer would choose. 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. It is one way to prevent a few thousands calls from angry customers after Microsoft releases an update to the redistributable. Their authors hold on updating to the latest runtime until they tested their app's compatibility with the new runtime. Some apps are very specific about the version of the Visual C++ dlls they require to make sure the app runs exactly as published. Uninstalling one Visual C++ redistributable could save you a few megabytes of disk space, but you risk breaking some apps in doing so.īecause 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. 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. sin and cos math functions and handling of common user interface elements like textbox or button). 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. Visual C++ redistributables are components shipped by app developers who use Visual C++ to write their software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |