Hello,
I've installed:
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
and got the following folders:
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a
I allready uninstalled the redistribute package but they continue overt...
I am attempting to author a merge module for use by multiple application installers to install a Win32 Shared SxS Assembly and its associated Policy. I'm using WiX 3.0 to generate the MSM and test MSIs.
So far it works fine on XP-SP3/Vista-SP2/Win7 for the first app installer that runs … but on XP-SP3 the second app installer fails bec...
Visual Studio 2010 installs version ...4974 of the VC9 runtime whose .pdbs are unavailable. How can I force my GME.exe to use an older VC9 runtime?
I've tried putting this into GME.exe.config:
<?xml version="1.0"?>
<configuration>
<windows>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity type="w...
:(
i can't install my msi file because of that. does anyone know why is that?
...
Hi all,
When I try to install my msi package I get an error only in Vista and 7. "Error 1920. Service ... (...) failed to start. Verify that you have sufficent privileges to start system services"
I get this error in Vista or 7 if I build my setup with C++ 9 CRT Winsxs MSM merge module
If I use C and C++ 7 runtime libraries it doesn't...
Hi all,
I had a problem installing my project on vista and 7 which I mentioned before here.
http://stackoverflow.com/questions/3617689/how-to-cope-with-install-error-1920-about-winsxs-merge-modules-in-vista-and-7
I see that post for a problem may be similar of mine, and there is a solutuion author tried.
http://stackoverflow.com/quest...
Got a fresh Win7 machine with VS2005 installed. I tried to start a MyApp.exe that is built with manifest that says in Manifest.bin:
...
<assemblyIdentity type="win32" name="Microsoft.VC80.MFC" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b">
</assemblyIdentity>
...
and the result was error mess...