Change "runtime library" from "Multi-threaded Dll" to just "Multi-threaded". In visual studio, it's the option in the project's propery dialog under C/C (under the Code Generation tab). If you actually have the source code to the EXE that you are trying to launch, you can completely bypass all of this "install msvcrt100.dll" noise by just statically linking to it. This isn't recommended, but won't run the risk of breaking other apps.Īnother alternative. Instead of copying MSVCRT100.dll into a system directory, copy it into the directory of the EXE app you are trying to launch that depends on this DLL. 01:41 PM 571,904 Microsoft_VC100_CRT_x86.msm <- This is likely the MSM you want if your app is 32-bit. C:\Program Files (x86)\Common Files\Merge Modules>dir *CRT*.msmĭirectory of C:\Program Files (x86)\Common Files\Merge Modules If you actually want to install the MSVCRT100 DLLs through a merge module within your own MSI - you can link your MSI to the MSMs that are located in the x86 version your "c:\program files\common files\merge modules" directory" (Assuming you have Visual Studio 2010 installed). Microsoft Visual C 2010 Redistributable Package (圆4) (Only if your app itself is 64-bit) Microsoft Visual C 2010 Redistributable Package (x86) (probably what you need for 32-bit and 64-bit os) This will properly install the MSVCRT DLLs in the proper directory such that all applications can use it. This is likely what you want your customers to run before installing your app. This links below point to the proper downloads for the MSVCRT100 installer.
0 Comments
Leave a Reply. |