Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    So, to be clear: I am not building the EXE, I am building a DLL to be run with someone else's EXE. Changing the platform target of the C# DLLs to Any CPU does not eliminate the warning. I'm wondering if this is a case of connect.microsoft.com/VisualStudio/feedback/details/728901/… -- I would ignore the warning itself but in fact the EXE is able to load the C# DLL but not the C++ DLL so I think this is a real problem. Commented Apr 17, 2012 at 17:15
  • Are you in fact using VS2010? It also wasn't clear at all that you couldn't load the C++/CLI DLL. What is the diagnostic? Update your questions with this essential info. Commented Apr 17, 2012 at 17:31
  • Hadn't posted about the load failure because I wasn't 100% sure it was connected, and on further debugging it turns out not to be. I am using VS2010. Updated question text. Very sorry for confusion Commented Apr 18, 2012 at 18:41
  • 1
    You didn't document any kind of error or exception related to loading the DLL. I cannot help you if you don't tell me what you know. Good luck with it. Commented Apr 18, 2012 at 18:44

default