PDA

View Full Version : Advice please



NewsArchive
08-08-2008, 01:43 AM
Hello,

I have some .NET modules that I am installing with my application. The documentation for the .NET
controls I am using say that I need to distribute GDIPLUS.DLL, MSVCP71.DLL, and MSVCR71.DLL. Where
should they go? I have searched a couple of machines, one XP, one Vista, and have found them in
several places. I would have thought the System32 folder, but that does not seem to work when I
mark them "never replace", they don't always install even when not in the System32 folder. Should
I just put them in the same folder as my other executables and not worry about other instances?

Thanks,

Tony

NewsArchive
08-08-2008, 01:44 AM
Tony,

> I have some .NET modules that I am installing with my application. The
> documentation for the .NET controls I am using say that I need to
> distribute GDIPLUS.DLL, MSVCP71.DLL, and MSVCR71.DLL. Where should they
> go? I have searched a couple of machines, one XP, one Vista, and have
> found them in several places. I would have thought the System32 folder,
> but that does not seem to work when I mark them "never replace", they
> don't always install even when not in the System32 folder. Should I
> just put them in the same folder as my other executables and not worry
> about other instances?

You should avoid placing a copy or using an existing copy of msvcr71.dll in
the system directory. Instead, your application should keep a copy of
msvcr71.dll in its application directory with the program executable.

Note, on Windows XP, Windows 2003 Server, etc. GDI+ is already available, so
you need not worry about gdiplus.dll. On older systems, also put it into
the application directory to avoid the "dll hell" problem.

You can't install a new gdiplus.dll over the system-supplied version because
it will fail due to Windows File Protection! Only a Windows update can
replace those protected files.

Hope this helps.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
08-08-2008, 01:44 AM
>
> You should avoid placing a copy or using an existing copy of msvcr71.dll in
> the system directory. Instead, your application should keep a copy of
> msvcr71.dll in its application directory with the program executable.

Friedrich,

Yes, it helps very much. What about MSVCP71.DLL, same as MSVCR71.DLL?

Thanks,

Tony

NewsArchive
08-08-2008, 01:45 AM
Hi Tony,

>
> Yes, it helps very much. What about MSVCP71.DLL, same as MSVCR71.DLL?
>

Yes, both MSVCP71.DLL and MSVCR71.DLL redistributables can go into the
application folder.

Friedrich