Building a .Net plugin with UnityEngine problem.

Unity Engine
1

Hey all, I’m trying to build a .Net plugin using the UnityEngine.dll.

If I build a generic plugin that doesn’t include UnityEngine in the references it builds fine.

Once I add the UnityEngine into my references it doesn’t build anymore.

I’m using MonoDevelop with the runtime version set to whatever and it still doesn’t build.

Any reason why this happens or any solution to get it to build?

Thanks,
Nathan

2

I’m not sure if I can actually help you, but it could be very beneficial if you elaborate on “doesn’t build anymore”.
I don’t think anyone will be able to diagnose the problem without knowing any of the symptoms.

3

Monodevelop doesn’t output a .dll file anymore, there are also no build errors or warnings.

4

The solution was I just opened the project in Visual Studio and built it there. Worked first time. :slight_smile:

5

I had the same problem building a DLL using MonoDevelop when including the UnityEngine.dll in the project - the program stopped outputting a .dll file right after unity was included. I found that using the latest official version of MonoDevelop + the latest GTK# package from Redirecting… worked just fine!
So just a heads up to others trying to do this (especially useful when your on a mac)