Deployment question
-
If I staticly link the MFC libraries, will a doc/view MFC application run on any Win32 system? It seems like Visual Studio.net comes with a new version of MFC. I read somewhere that some of the controls relies on IE 4, is there anything else I should be concerned about? If I don't staticly link the libraries, what versions of windows will still be able to run the application? Thanks! - Anatari
-
If I staticly link the MFC libraries, will a doc/view MFC application run on any Win32 system? It seems like Visual Studio.net comes with a new version of MFC. I read somewhere that some of the controls relies on IE 4, is there anything else I should be concerned about? If I don't staticly link the libraries, what versions of windows will still be able to run the application? Thanks! - Anatari
With VC 6, I've been able to run a non-static(dynamic) linked mfc app on every platform from win95 up through xp. However, there have been cases (not all) on certain NT4.0 installations that I got some kind of 'ordinal' error. After scratching my head for a few minutes, I realized that the MFC42.DLL on the NT 4.0 box was probably out of date. Copying a new one manually to the box fixed the problem. This, I believe, was also fixed by doing a later service pack. Static linking will guarantee functionality. HOpe this helps. Paul Oss
-
If I staticly link the MFC libraries, will a doc/view MFC application run on any Win32 system? It seems like Visual Studio.net comes with a new version of MFC. I read somewhere that some of the controls relies on IE 4, is there anything else I should be concerned about? If I don't staticly link the libraries, what versions of windows will still be able to run the application? Thanks! - Anatari
The only problem I have struck is if I was forgetful enough to try to run a Debug build on a 'virgin' machine. Then it will natually report an error that MFC42D.dll can not be found. Windows ships with the latest release versions of MFC, both the MFC42 with is for VC6 and MFC7 which is used with .NET. Happy programming!!
-
The only problem I have struck is if I was forgetful enough to try to run a Debug build on a 'virgin' machine. Then it will natually report an error that MFC42D.dll can not be found. Windows ships with the latest release versions of MFC, both the MFC42 with is for VC6 and MFC7 which is used with .NET. Happy programming!!
None of the distributions of Windows 2000 or XP I've seen in recent months, including the ones that come with the MSDN Universal, or any of the service packs (Win2000SP3 or WinXPSP1), include the MFC7 libraries. If you build an MFC app with VS.NET, you've got to install the libraries on the target machine.
Software Zen:
delete this;