Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have exactly the same problem asked here.
Problem using Managed C++ (.Net 2.0) in .Net 2.0 project in VS2010.
Basically I have a C++/CLI project in .NET 2.0 and it indirectly references some 4.0 version dll via MFCMIFC80.DLL.
The only solution the person found was to delete MFCMIFC80.DLL.
How safe is that? Is there any other way to do this?
Solution:
The C++ project was using the v100 Platform toolset. This makes it depend on 4.0 .NET versions of some libraries.
Changing the toolset to v90 solves the problem.