Do you have to "pair" DLLs?

[davemassey]

Hi all! I've been told that certain DLLs from MSoft have to be deployed in "pairs" based on version numbers. So, you have msvcrt.dll and msvcirt.dll you'd have to ensure that they are deploy with the same version numbers. Does that sound correct and how closely would the version numbers have to match?

Thanks!

Dave

 

[VincentP]

Something I learned recently: Do NOT deploy msvcrt.dll. It comes with the OS. I have some clients who had to rebuild their Win 98 OS because I had included my Win XP version of msvcrt.dll in my installation package.

The following is about Visual Basic:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;330314

but this part is important: "To prevent the problem from occurring in the future, do not redistribute MSVCRT.dll with your setup package. MSVCRT.dll is in the Microsoft C Runtime Library, and MSVCRT.dll is installed with the operating system. Only update MSVCRT.dll by using operating system service packs."

I hope this helps, even though it is not quite the question you asked.

Vincent

 

[PerFnurt]

See

http://support.microsoft.com/default.aspx?scid=kb;en-us;296551

You should have requirements on the target system your application is to be deployed to.

You should not try to "upgrade" peoples OSes just so your application can run there. Of course to make it convenient for your customer you could perhaps supply your installation with an "official" OS upgrade gizmo but you should not try to upgrade one file here or one file there by yourself.

Bottom line: Don't fiddle with the customer's OS and you should be fine.

/Per
[sub]
"It was a work of art, flawless, sublime. A triumph equaled only by its monumental failure."[/sub]

 

[davemassey]

I hadn't really thought about that, but you're right: it's not cool to drop "updated" versions of system files onto a target machine during an install -- so I'll have to visit that issue in the install script. Thanks.

Dave