![]() ![]() ![]() I cannot imagine how frustrated I would become if I could not use them. Not having these tools is pretty much a dealbreaker for dlls for me. ![]() And then I tried some typical operations like go to definition, refactor, find all references, and it became pretty clear (like you noticed) that the reference was not a project reference (since clearly, how could Unity know). I moved a small number of project-agnostic support files that are highly shareable to the dll. Recently the thousands of loose scripts I have developed over the years have driven me to the point where I cannot take it anymore. Have you figured out how to make this work? I've had a dll I setup years ago, that I never used beyond testing it with a hello world and that I could debug it. I am running Visual Studio 2015, Resharper 2016.2.2 and Unit圓d 5.5. Is there a way to let Resharper/Visual Studio know that any calls made to the compiled logic dll should be matched to the project instead? When I, for example, right-click a method in the logic library and select "Find all references" it shows those from the logic project itself and calls from the console application as well, but it obviously does not show calls in the client since there (technically) aren't any. ![]() My issue is that I can not get VS or Resharper to recognize that my logic library project and the (compiled and referenced) DLL in the Unity project are actually the same thing. The server application however has a normal project reference to the logic DLL. Unity then automatically adds a reference to the compiled DLL to the VS project for the game client. Since it is not possible to directly reference another VS project in the Unity project, I have to copy the logic library post build to a Unity asset folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |