Comments on: Side-by-Side Horror

By: Gary kaizer

Gary kaizer — Wed, 04 Feb 2009 20:08:03 +0000

In order for your friend to run your application without running a setup wizard you should use the manual deployment method for the new libraries leveraged in VS2008.

This is meant for x86 machines, but can be easily modified:

1) Download and run http://www.microsoft.com/downloads/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en. Which should install the side-by-side assemblies needed. (vcredist_*.exe where * is the processor they have: x86, IA64, x64)

2) If you are using any custom libraries include them with your exe and either put them with your exe or in the folder named after the library (so MFC90 library would go in the Myapp\MFC90\).

3) Run you executable.

By: bollywood fun

bollywood fun — Sun, 01 Feb 2009 12:14:16 +0000

Look at, and compare, the sizes of the resulting MinGW and MS VC++ executable files and you will see the difference.

By: lilJ0hn

lilJ0hn — Thu, 04 Dec 2008 21:25:35 +0000

Wow…no one has mentioned where you really went wrong…
c++

By: Doug

Doug — Wed, 01 Oct 2008 18:46:30 +0000

You might consider creating an install package that also installs the c runtime.

Take a look here for more information:
How to redistribute the Visual C++ Libraries with your application
http://blogs.msdn.com/vcblog/archive/2007/10/12/how-to-redistribute-the-visual-c-libraries-with-your-application.aspx

Of course I have found it to be a little flakey. In some cases it will install only the amd64 bit version on an OS that is 32bit but running on a 64 bit capable processor. I haven’t found a solution to that yet, very annoying.

By: radioman

radioman — Thu, 18 Sep 2008 16:37:34 +0000

..my favorite stuff, i love it ;} http://img162.imageshack.us/my.php?image=vsversionao0.png

after each ServicePack visual studio use old runtime, wtf ;/

last time i solve it by clean windows reinstall and then vs install, and then sp1 install. but if you install sp1 later you have incorect versions ;{

By: HEX

HEX — Tue, 09 Sep 2008 10:50:00 +0000

I can build console project in VS2005 and VS2008 with /MTd code generating. Both 2005 and 2008 have same problems. The only diffrence between is, I don’t know how to build a win32 form application in VS2008 but I do know how to do it in VS2005. (but I can use VS2005 project v VS2008 and it works for the most of folks)

By: Fred

Fred — Tue, 09 Sep 2008 02:09:15 +0000

And, I spent many days wrestling with this BIG problem. After this horror don’t want to use any more f*cked M$ products.

By: Christian

Christian — Wed, 14 May 2008 13:08:58 +0000

This was very helpful. I spent many hours wrestling with this problem.

By: giry

giry — Wed, 30 Apr 2008 08:58:37 +0000

Thx for the article, i find some answers here.

By: Tobias

Tobias — Sun, 20 Apr 2008 03:35:39 +0000

“Unfortunately, the manifest file that is generated contains references not only to VC90 DLLs, but also to VC80 DLLs.”

ok, reason is clear in hindsight: VS derived the VC80 DLL dependency from the linked SDL.

I rebuilt SDL 1.2.13 (current stable) using VS9 (needed to download/install DirectX SDK for that). After that, the second dependency is gone, embedding the manifest works and side-by-side installation of the Microsoft.VC90.CRT folder works (at least on a fresh XP SP2 machine).

For earlier systems it is likely that you then need to add the path to the Microsoft.VC90.CRT folder to PATH.

The following is also working: put the _contents_ of the Microsoft.VC90.CRT folder in the same folder as your app. You’ll need the manifest! Probably, this way on older systems than XP SP2, this works without setting PATH. I don’t have an older system around, so I don’t know ..