   Visual Studio 2005 /MD Horrors
  Hello, If I compile a program using the Multi-Thread (Debug) DLL option, it runs on any computer with VS20005, but on computers without, I get a message saying "the program is incorrectly configured". Up until now, I've been handling this problem by using /MT instead. Now my old lazyness haunts me. I'm using some libraries in my app. that requires /MD (SDL for instance). I've tried recompiling SDL with /MT instead of /MD, which I've read should solve the problem, but it did not.Ideally, there would be some way to enable the use of /MD-compiled programs on non-VS2005 computers. Is there? As you might have detected, I'd like to avoid recompiling as many external libraries as possible, unless this is very superior to the precompiled ones.Thanks!   
  My reply here should clue you into an answer   ;  Thanks! (I did try to search for this!)   ;  You shouldn't need to set up an installer with MSI (as in the linked reply): if you want to be lazy (or if you dislike installers and prefer software distributed in nice simple zip files), just copy the four files (three .dll, one .manifest) from VC\redist\x86\Microsoft.VC80.CRT into the same directory as your .exe. (And make sure you haven't disabled manifest generation in the VC2005 project - it should be on by default.)That works fine for me in Windows 2K and XP, and I believe it would in other versions too.   ;  Excors: Thanks, that does make things a lot simpler. In fact, this was the solution I was hoping for. You all rock.   ;  You can not redistribute Microsoft's debug runtimes in any form legally, except for a static lib built into the program. If you want to debug a build on another nondevolpment machine, then you must use a release build or else link with the static runtimes.   