Thread: mfc420d.dll

Project -> Settings -> General -> Microsoft Foundation Classes: "Use MFC in a Static Library"

In the project view (the tree view), right-click the project and select properties.

Originally posted by XSquared
Project -> Settings -> General -> Microsoft Foundation Classes: "Use MFC in a Static Library"

Is that how you're supposed to fix that mfc42d.dll problem??? I'm glad you asked this question, GodLike, because I encountered the same problem and ended up just installing the missing DLLs on the other box...
I just tried compiling with "Static Library" instead of shared, but now I have a link error because nafxcw.lib is not found... Did you ever have this problem XSquared? Do you know how to resolve it? Is it as simple as maybe copying the file from the CD? hmmm...

Learning Edition's Custom AppWizard Can Generate Fatal Link Error LNK1104

Custom AppWizard allows you to create custom appwizards that rely on the MFC Static Libraries. The MFC Static Libraries are included only in the Professional and Enterprise Editions of Visual C++. Attempting to use the MFC Static Libraries in the Learning Edition will result in a fatal link error LNK1104 on one or more of the following libraries:

- nafxcw.lib
- nafxcwd.lib
- uafxcw.lib
- uafxcwd.lib
- nafxis.lib
- nafxisd.lib

The reason I keep getting this error is that I have the Learning Edition of MSVC 5.0
Ugh... I really don't want to fork out the cash for 6.0 (professional or enterprise edition).. What am I to do? I wish I could easily (and cheaply) upgrade to 6.0.... Ugh.

Anyone want to email me a copy? Thanks.

Code:

Is that how you're supposed to fix that mfc42d.dll problem???

No, the problem you really have is that you try to distribute the debug version of the app, which requires the debug version of the MFC dll.
Compile as "Release" and distribute that file.

Of course you don't have the legal right to distribute any file.

Originally posted by CornedBee
No, the problem you really have is that you try to distribute the debug version of the app, which requires the debug version of the MFC dll.
Compile as "Release" and distribute that file.

Of course you don't have the legal right to distribute any file.

Are you saying that building using MFC in a static DLL does not fix the problem of someone trying to run an app without the MFC libraries?

Actually, if I recall correctly (this was about 3 months ago), I did in fact build in release. I don't remember the actual dlls that were missing (they might not have been the *d.dll files)... Eh. Either way, I just downloaded MS Visual Studio 6 Enterprise Edition last night, so my CString incompatibility and my learning edition limitations are behind me (buddha-willing)...

Hey anyone have a copy of DWMAPI32.lib in your VisualC\lib directory you can zip up and email me? The one in the zip I downloaded was corrupted (or some such thing) noting a CRC error...

Originally posted by LuckY
Are you saying that building using MFC in a static DLL does not fix the problem of someone trying to run an app without the MFC libraries?

There's a difference between static linking of the libraries and with the option to tell the compiler to create a release build (optimised without the extra burden of the debug code). The static linking option allows you to not worry about the MFC dlls when redistributing, but is only available in VC++ Pro or above

Originally posted by LuckY
Hey anyone have a copy of DWMAPI32.lib in your VisualC\lib directory you can zip up and email me? The one in the zip I downloaded was corrupted (or some such thing) noting a CRC error...

Doesnt the disk for VC++ have this? Cant you reinstall?
If not, it should be part of one of the SDK (Maybe the platform sdk) available free from MSDN

Originally posted by Fordy
There's a difference between static linking of the libraries and with the option to tell the compiler to create a release build

I appreciate your restating it, but I was already aware of your point. I was just trying to make another point. CornedBee said that statically linking to MFC was not required to run an app on a box that doesn't have MFC libraries; he said you just have to distribute a release build as opposed to a debug build which very obviously has nothing to do with the MFC libraries. Side note: Is VC++ enterprise "above" the pro version? Just curious because static MFC linking is available to both.

Doesnt the disk for VC++ have this? Cant you reinstall?
If not, it should be part of one of the SDK (Maybe the platform sdk) available free from MSDN

Actually, I don't have an actual disk. As I previously stated, I downloaded MS VisualStudio 6 last night and that file in the zip was corrupt or some such thing... You did point something out to me though; it may be on my old-fashioned MSVC 5.0 disk that I do have. I'll have to check that out when I get home.

Pro and Enterprise are different versions.

Originally posted by CornedBee
Pro and Enterprise are different versions.

Gee, really? Yeah, I know that cornedbeef. Fordy said "only available in VC++ Pro or above." I just asked if Enterprise is "above" Pro or if Pro is "above" Enterprise, you sociopath.