Printable View
MSVC2005 allows you to choose between using the lib and dll version of the Run-Time Library. With static one, required code will be included to your exe or dll. With dynamic one, a dll is required at run time, but it will make exe smaller.
What are each one's benefits?
You basically outlined the pros and cons of each.
I also guess static ones will load faster.
Not necessarily. The bigger executable will take longer to load from disk into memory. The DLL will probably already be loaded, and just needs to be made available to the new process. On the other hand, the loader needs to do more work for the DLL than for the static lib.Quote:
Originally Posted by siavoshkc
The statically linked program will take more physical memory from your computer, because it doesn't share its runtime with other programs.
Also your statically linked executable is just that: the code it's built with is the code it will always have. With the dynamic linked version, any updates to the dlls should positively affect your application (mostly; such updates may occasionally and unfortunately break it, too). It's for this reason that ms specifically recommend dynamic linking to ensure that, in particular, security updates propagate to your applications. Obviously, other improvements to the dll code itself will result directly in corresponding improvements to your applications' performance - in theory, anyway.