- Home /
Unity 5 Managed DLL considered Native
I have a DLL that I need to use to interface with a physical device. It comes in a few different formats - Managed with .NET 4.0, Managed with .NET 2.0, and Unmanaged (Unity's "Native"). I'm trying to use the Managed 2.0 DLL for my project, however Unity recognizes it as a Native Plugin, rather than the Managed Plugin that it is (or at least that I'm told).
I can manually reference it in the Visual Studio solution, and it works just fine, but it still throws a compiler error saying that the namespace doesn't exist. Are there any workarounds or settings that need to be applied to use this Plugin with my project?
Unfortunately, I don't have a solution for this myself, yet. Happened to me after getting a project via GIT and a DLL that actually is managed is recognized wrongly as native. In the main project and two other machines where I did the same operations (one of them being a $$anonymous$$ac), it worked without a problem. But on two machines, I'm having this problem.
$$anonymous$$aybe it's a mixed mode assembly which contains both, managed code and unmanaged code? $$anonymous$$ost driver / interface DLLs are either wrappers for a native library or contain native code themselfs in order to communicate with custom hardware.
Your answer
Follow this Question
Related Questions
Referencing a DLL in C# 0 Answers
Using Native C++ dll in Unity 1 Answer
Are calls to C++ DLL handled asynchronously? 1 Answer
How do you use a class from a .dll file? 1 Answer
Import (mixed assembly) managed C++/CLI DLL plugin 0 Answers