The application has failed to start....
-
My application fails with "This application has failed to start because the application configuration is incorrect. ..." on other computers. I know that Microsoft Visual C++ 2008 Redistributable Package or Creating setup.exe helps, but I need another solution. I want my program to work without installers and packages. What should I change in project properties? PS:I am working in Visual Studio 2008.
-
My application fails with "This application has failed to start because the application configuration is incorrect. ..." on other computers. I know that Microsoft Visual C++ 2008 Redistributable Package or Creating setup.exe helps, but I need another solution. I want my program to work without installers and packages. What should I change in project properties? PS:I am working in Visual Studio 2008.
If you are working with COM you should check if the your custom COM Components dlls are being registered properly. You could make two scripts to do this, for exmple Reg.BAT regsvr32 ProcessLibrary.dll regsvr32 ProcessLibraryPS.dll UnReg.Bat regsvr32 /u ProcessLibrary.dll regsvr32 /u ProcessLibraryPS.dll
JO :)
-
If you are working with COM you should check if the your custom COM Components dlls are being registered properly. You could make two scripts to do this, for exmple Reg.BAT regsvr32 ProcessLibrary.dll regsvr32 ProcessLibraryPS.dll UnReg.Bat regsvr32 /u ProcessLibrary.dll regsvr32 /u ProcessLibraryPS.dll
JO :)
-
I use "Standard windows libraries" with "common language runtime support" As I understand MSDN, I should register msvcm90.dll, msvcp90.dll, msvcr90.dll on computer to run my application. Am I right?
No, The dlls you should register in order to use them are the ones of you COM Components (i assumed you were developing COM somponent for the Forum name :D). You could Also check for missing dlls in you installation directory with the dependency walker, this little program checks yor .exe for missing dependencies so you could copy to the instalation dir the files missing (ie: msvcm90.dll, msvcp90.dll, msvcr90.dll ) You could download dependencywalker from: http://www.dependencywalker.com
JO :)
-
No, The dlls you should register in order to use them are the ones of you COM Components (i assumed you were developing COM somponent for the Forum name :D). You could Also check for missing dlls in you installation directory with the dependency walker, this little program checks yor .exe for missing dependencies so you could copy to the instalation dir the files missing (ie: msvcm90.dll, msvcp90.dll, msvcr90.dll ) You could download dependencywalker from: http://www.dependencywalker.com
JO :)
-
After using dependencywalker I understood that my program requires msvcm90.dll, msvcp90.dll, msvcr90.dll. I copied them into directory with my .exe file, but it didn't helps. Maybe I should copy them to some system folder&
Try installing the Microsoft Visual C++ 2008 Redistributable Package that installs and registers the dlls you need. If you are using additional COM components you should also register the associated dlls with regsvr32. C++ redist Link: http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en
JO :)
-
Try installing the Microsoft Visual C++ 2008 Redistributable Package that installs and registers the dlls you need. If you are using additional COM components you should also register the associated dlls with regsvr32. C++ redist Link: http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en
JO :)
Just for clarification, this isn't a COM error. It is caused by an Fancy MS feature called Windows Shared Side by side Assemblies (or any other weird name, so apologize). See http://msdn.microsoft.com/en-us/library/aa375996(VS.85).aspx[^] Never wondered about the C:\WINDOWS\WinSxS directory? The worst thing you can do is copying the 9.0 dlls to your exe path, or simply registering them in your system directories since this can cause third party applications to fail!!! The MS way would be redistributing the dlls with their own created merge modules located somewhere in the Studio folder. (I'm too lazy to look up the correct location, if you can't find them PM me ). So long, Stefan
-
Just for clarification, this isn't a COM error. It is caused by an Fancy MS feature called Windows Shared Side by side Assemblies (or any other weird name, so apologize). See http://msdn.microsoft.com/en-us/library/aa375996(VS.85).aspx[^] Never wondered about the C:\WINDOWS\WinSxS directory? The worst thing you can do is copying the 9.0 dlls to your exe path, or simply registering them in your system directories since this can cause third party applications to fail!!! The MS way would be redistributing the dlls with their own created merge modules located somewhere in the Studio folder. (I'm too lazy to look up the correct location, if you can't find them PM me ). So long, Stefan
C:\Program Files\Common Files\Merge Modules
Scot Brennecke Software Developer VC++ MVP