Referenced dlls not updating
Referenced dlls not updating - is apolo ohno dating anyone
Unity must reload the updated DLL, which also takes time.
In this article I'll explain the benefits that will make you want to use DLLs.
Indeed we can make use of DLLs that have been created for us by other developers. Many of the packages for sale on the Unity Asset Store include DLLs rather than source code. NET libraries that can be installed through nuget (at least the ones that work with Mono/Unity). I'm going to make arguments for and against using DLLs with Unity.
In this line of work there are no perfect answers, we must do our best given our understanding and knowledge at the time and aim to make the right tradeoffs at the right times.
But this has two downsides: But there is an alternative: Add a reference to the compiled DLL by clicking "Add Reference..." and choosing from the tab "Browse".
This seems to work fine initially, until the target DLL is updated and its version number changes.
Then I'll cover the problems that will make you regret that decision.
Finally I'll show you how to get the best of both worlds: using source code where it makes sense and using DLLs where they make sense.Now I must show you there are real benefits to working with DLLs.Here is another pitfall of using DLLs that is worth considering. Compiling a DLL from source code and copying it to your Unity project takes time.Then all hell breaks loose and there is no way to fix this - from the GUI. In my previous article I talked about Unity and Visual Studio: using Visual Studio to edit and maintain your Unity code.I've heard it said that there are no right decisions, only less worse decisions.