#Coding for Unity in VB.Net

1 messages · Page 1 of 1 (latest)

craggy quail
#

I haven't since then. Unity's code base isn't CLR compliant (wasn't then, still isn't now), so they still rely on case difference in naming that VB doesn't like. As I recall, I had to import a bunch of DLL's from Unity's installation for intellisense to work and get VB DLL's to compile. Once you have the DLL's built, Unity will should accept them. What I did back then was create the Unity project and open the solution in Visual Studio, and then add a VB project to that solution, link the DLL's for Unity, and code from there. I set the destination folder for builds to be a specific folder within the Unity project, so as soon as you build and switch back to unity, it picks up the new DLL.

jagged rampart
#

But how do I "just add references to the Unity DLL's"?

#

Where are the needed dlls?

jagged rampart
#

I think I got it working, but everytime I reopen a script the vb project vanished from the solution Hmm

craggy quail
#

I don't know of any other engine that will take in .Net DLL's