Re: msvcr90.dll in application directory
The disadvantage of Alex's suggestion is that your executable will grow in size by all of the CRT
functions you are using. If Microsoft then publishes a fix for any of the CRT functions you used,
you must rebuild and redistribute your executable. On the other hand, if you use the
redistributable DLLs that are installed be the package first mentioned, when MS publishes a fix,
your program will benefit from it without having to rebuild.
The other method of copying the "Microsoft.VC90.CRT" folder (including the manifest) as a subfolder
of your program folder is called "app local" deployment. It suffers from almost the same pitfalls
as the static linking (no automatic maintenance), but at least you don't have to rebuild -- you must
just replace the DLLs yoursolf when fixes are published. Some choose this option because it doesn't
require admin access to run an installer (xcopy will do it).
Scot
"GiuseppeDini" <vvene@libero.it> wrote in message
news:51a79c98-1756-4dd5-be9d-e6c8a2b723b3@n21g2000vba.googlegroups.com...
On 21 Mag, 10:08, "Alex Blekhman" <tkfx.REM...@yahoo.com> wrote:
No, it won't be right thing to do.
Your friend must install VC++
runtime libraries in ordert ot run your program:
"Microsoft Visual C++ 2008 Redistributable Package
(x86)"http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e0...
ok
Alternatively, build your program with CRT statically linked, then
no special libraries will be required on the destination machine.
So I have to use the /MT option and it will create a standalone file
which contains all the code I need?
I've read this page: http://wiki.allegro.cc/index.php?title=Visual_C%2B%2B_Express_2005#Deployment
It seems to suggest to copy the folder "Microsoft.VC90.CRT" in .exe
directory and it will work, but maybe I've been mistaken.
Thank you for your help!
Giuseppe