   Unable to launch EXE at all
  I just submitted to a friend a program I am working on.He replied with this image :http://jaguargordon.free.fr/shot/lol.jpgI don't know what the exact message would be in englishbut it can be read as : "This application was not ableto start because its configuration is incorrect. Youmay consider to reinstall."I sent him MSVCR80D.DLL to test (as I use vs2005 andthe exe was built in debug mode) with no success.Building in Release mode with the appropriate msvcr80.dlldoesn't work either.What do you check first when you get this kind of error message ?   
  Take a look at the exe in Dependency Walker 2.1 (free utility), you might need to ship another dll beside MSVCR80D.DLL.   ;  Thanks for the link, I'll need this tool sooner or laterbut my problem have an dumber solution. I didn't know Ihad to include "Microsoft.VC80.CRT.manifest" with the DLL.Do you guys know how to link to the old MSVCRT.DLL ?;  In the Proj Properties -> C/C++ -> Code Generation, try chaging the Runtime Library from /MTd to /MT. Doing static compilatin eliminated a problem with releasing VS2005 EXE's for me. Though your exe gets bigger, and they poo-poo the practice of not using future releases of DLL's.   ;  I think, that the best solution for you is to tell your friend about this link:http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=enFrom this page, he will be able to download and install all MSVC2005 runtimes, and the installer will take care of all manifests.   ;Quote:Original post by Paulius MaruskaI think, that the best solution for you is to tell your friend about this link:http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=enFrom this page, he will be able to download and install all MSVC2005 runtimes, and the installer will take care of all manifests.Thanks for the link but my friend is actually beta-testing a demo which should pop on the internet when it's done. I won't require people to download 3rd party libraries nor will I force them to install my app as an .MSI package.I still don't understand why I must provide "Microsoft.VC80.CRT.manifest" with "msvcr80.dll" I already ship ... It doesn't make sense to me : aren't the manifests embedded ?   ;  It's a change in the policy of how MSVC2005 links against the runtime.It's clearly stated in the EULA that you can't redistribute the runtime libraries yourself(So giving him the .DLL, is a violation of the EULA) without the installer.Before MSVC2005, you should ship the DLLs with it, and it would automaticly bind to it if it were in the directory of your exe. However, this has changed, and currently it's only load the DLL from the System32 folder(I think) in the Windows folder itself.In other words: You must provide the installer. IF you want to make you app downloadable, provide a small isntaller that runs this installer silently in the background.There is no other way around this...Toolmaker   