This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 99%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHD%3C/text%3E%3C/svg%3E)
Hi There,
Greetings!
I have some clarifications on the following DLL's.
Mfc42d.dll
MFCD42D.dll
MSVCRTD.dll
MFCO42D.dll
These DLL's supports "debugging" (software testing) during software development. The Release versions should not make use of these debug dll files.
Please clarify these DLL's if not there what is the impact on Application.
A release build of an MFC application should not require anything other than the release version of any DLL dependencies. The absence of debug version DLLs should have no impact on the release build of an MFC Application.
May i know the use of debug version DLLs, how it will help me in debug mode ?
Generally speaking, debug builds include runtime checking to identify error conditions and provide relevant information to a developer. Also, debug builds are typically created without using compiler optimizations so that it is easier to set breakpoints, step through source code and examine variables while debugging.
Debugging is a pretty broad subject. You might want to take at Microsoft's documentation -- Debugger documentation - Visual Studio (Windows)
I have one final request.
please confirm all these DLLs are debug versions?
Mfc42d.dll
MFCD42D.dll
MSVCRTD.dll
MFCO42D.dll
Also, in the first answer you gave, "A release build of an MFC application should not require anything other than the release version of any DLL dependencies.
I understood the released version does not require anything, when it got build in release mode.
Microsoft's naming convention is to append the letter "D" or "d" to the name of a dll to indicate that it is a debug version. For MFC library naming conventions refer to MFC Library Versions.
To avoid DLL dependencies an application can link with static libraries. Debug builds should link with debug versions of a static library and release builds should link with a release version of a static library. Applications that link with static libraries are self-contained (i.e., no DLLs are needed for those libraries)
However, since you mentioned various DLLs in your question it appeared that you were asking about creating an application that was intended to use the shared MFC Dlls instead of static libraries. This is the DLL dependency that I was referring to.
The DLLs were released around 1998. with 4.21 versioning, does it continue to support with the current and future windows versions?
I suggest that you use a modern and supported version of Visual Studio.
MFC is available and supported in these versions but you will need to migrate your code base to any new and supported version that you decide to use.
I have migrated my code to Visual Studio 2019 version looking forward to build in 2022 Version, and in "Individual Components" I have installed MFC v14.29(16.10) Version, and the build is successful. Is it a healthy move keeping these DLL's Mfc42d.dll, MFCD42D.dll, MSVCRTD.dll, MFCO42D.dll.
Is it a healthy move keeping these DLL's Mfc42d.dll, MFCD42D.dll, MSVCRTD.dll, MFCO42D.dll
Your dlls from 1998 have not received security updates for many years. In my view it's time to leave them behind.
I Understand the Visual Studio 2019 or 2022 has all the required set of components. As it is MFC dependent application the modern version of Visual Studio can do the job for me!
Please guide me Is my understanding is correct on that perspective on modern versions of Visual Studio.
I have no knowledge of the projects you work with and the technologies that are used. I cannot provide any guidance in this matter.
It is your responsibility to identify your needs and determine if modern, supported versions of Visual Studio and other currently supported technologies can satisfy them.
It was very nice interacting with you, I have learnt many things from you.
You were so kind enough to clear my doubts.
Thank you very much!