Custom Dlls and refenceres to Unity Dlls

Unity Engine
1

Hi guys.

I’ve updated my project from 2018.0.b3 to 2018.0b8 and noticed that the Library/UnityAssemblies/ folder is not present anymore. That was a very nice folder (I think it was introduced in 5.x or so) as all necessary Unity Dlls were located there, which are used by the project. I’ve referenced the Unity Dlls in that folder for my own custom Dlls projects and when updating the project to a different Unity version, all I had to do is update the project and build my custom Dlls and everything was fine.

Now that the folder is gone, I wonder how we are supposed to reference Unity Dlls in our custom projects (outside of the Unity project itself). Actually I won’t be very happy if I have to update the references to the Unity Dlls everytime I install a new Unity version.

Any thoughts on this one or do I miss something here?

Thanks for help!

2

Hi

The Library/UnityAssemblies folder is a Visual Studio Tools for Unity (VSTU) feature. It was removed in VSTU 3.4.0.2:

3

I see. Thanks for pointing that out, wasn’t clear to me. Nevertheless stands the question, how can I solve the problem in an elegant way? I don’t like the idea to change the reference paths all the time I install a new (beta) version of Unity.

Just to make my problem more clear (can’t believe I’m the only one with that problem), my project structure looks like:

  • ProjectFolder

  • CustomGameLogic

  • GameLogicProject (depends on the Unity DLLs used in the project)

  • UnityProject

  • Assets

  • Plugins (my game logic DLL is copied here after building)

  • Library

4

The way I would do is to use EditorApplication.applicationPath to locate the .dlls and patch the .csproj files from a MenuItem or similar in Unity.

2 Likes