mfc installation dependencies???
-
I used dependency walker to check the dependencies of my static mfc application, and got a list of core and other dependencies. I'm leary about including too many of these in my installation utility, so I was wondering if there is a list of dll's by OS (Win2000, Win95...) that are guaranteed to be present? Any other comments/cautions regarding distributing dll's with an application would be welcome! :) Thanks.
-
I used dependency walker to check the dependencies of my static mfc application, and got a list of core and other dependencies. I'm leary about including too many of these in my installation utility, so I was wondering if there is a list of dll's by OS (Win2000, Win95...) that are guaranteed to be present? Any other comments/cautions regarding distributing dll's with an application would be welcome! :) Thanks.
It's safest to include them anyway because the DLLs you require might not be the same version as in the OS. The installer will do a version check and only if the version is newer will it overwirte it. Regards, Nish p.s. One brute force technique I've used is to run my application on a fresh install of each OS :-O
Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]
-
I used dependency walker to check the dependencies of my static mfc application, and got a list of core and other dependencies. I'm leary about including too many of these in my installation utility, so I was wondering if there is a list of dll's by OS (Win2000, Win95...) that are guaranteed to be present? Any other comments/cautions regarding distributing dll's with an application would be welcome! :) Thanks.
Yup, check out Microsoft's DLL Help Database". (If the link doesn't work, do a search for "DLL Help Database" on http://msdn.microsoft.com ) You can enter in a DLL name, and it will tell you every product and OS that it is included in. You should also use Windows Installer and merge modules to deploy MFC runtimes, instead of just doing a file copy. Hope this helps! Jerry Dennany
-
I used dependency walker to check the dependencies of my static mfc application, and got a list of core and other dependencies. I'm leary about including too many of these in my installation utility, so I was wondering if there is a list of dll's by OS (Win2000, Win95...) that are guaranteed to be present? Any other comments/cautions regarding distributing dll's with an application would be welcome! :) Thanks.
I don't know where to find a list, but the ones that you typically have to ship usually start with m, like msvcrt.dll and mfc42.dll. My recommendation is to install these in the same folder as the application. This will ensure that your app runs with the proper DLLs and that you don't possibly break other apps by overwriting DLLs in the system32 folder. Regards, Alvaro
That which does not kill me postpones the inevitable. -- despair.com
-
I don't know where to find a list, but the ones that you typically have to ship usually start with m, like msvcrt.dll and mfc42.dll. My recommendation is to install these in the same folder as the application. This will ensure that your app runs with the proper DLLs and that you don't possibly break other apps by overwriting DLLs in the system32 folder. Regards, Alvaro
That which does not kill me postpones the inevitable. -- despair.com
I've seen other applications install the mfc dll's in their folders, but that seems risky to me. Here's my thinking... You may have a down rev version of a particular dll. If you install it in your own directory, and your app happens to be the first one to use it, the OS will load it up. The next app that needs the dll (maybe the more current one that's in the system folder) will get the down rev one, and poof... Could be a problem. Does that seem reasonable? If so, then you should install the dll in the windows "system" directory, and only install if your dll is a more recent version.
-
Yup, check out Microsoft's DLL Help Database". (If the link doesn't work, do a search for "DLL Help Database" on http://msdn.microsoft.com ) You can enter in a DLL name, and it will tell you every product and OS that it is included in. You should also use Windows Installer and merge modules to deploy MFC runtimes, instead of just doing a file copy. Hope this helps! Jerry Dennany
Great! I think that's what I'm looking for. The link worked, I'll take a look at it now. Thanks
-
Yup, check out Microsoft's DLL Help Database". (If the link doesn't work, do a search for "DLL Help Database" on http://msdn.microsoft.com ) You can enter in a DLL name, and it will tell you every product and OS that it is included in. You should also use Windows Installer and merge modules to deploy MFC runtimes, instead of just doing a file copy. Hope this helps! Jerry Dennany
Oh... I am using InstallShield, and only replacing shared files if the files I'm replacing are older than the one's I'm installing.