Yuck, this is ugly. I was wondering what will happen after Microsoft drops side by side to install the runtime libraries for VS2010. It seems clear that interwebs are full of this installer error. The biggest victim, apparently, is Microsoft itself, when Streets and Maps are not installed.
I don't know any security patches, so I have to guess that you have not updated SP1 yet. And your customers use the vendor product that did it. This is a battle you'll ever lose. Consider using local application deployment for DLLs by copying them in the same directory as your main EXE. Just copy them from the vc / redist directory before you place the installation package together, you do not need to specify the necessary condition. You will need:
- msvcr100.dll and msvcp100.dll for regular CRT
- atl100.dll if you are using ATL
- mfc100.dll, mfc100u.dll, mfcm100.dll, mfc100u.dll if you are using MFC (u = Unicode, m = managed)
- mfc100xxx.dll where xxx is code with a 3-letter letter if you use MFC on a non-English computer.
- vcomp100.dll if you are using OpenMP in your code.
The only drawback is that they will not be updated if there is a security fix. This can be an advantage, depending on which color glasses you wear. If you are not comfortable, then maintaining an machine that creates an updated installation package, including the inclusion of Windows Update, is an important requirement.
source share