- Home /
How to avoid unity plugins long processing time
In our workflow we have a big external (out of unity folders) code base on which we are working with visual studio. A lot of the code is used out of Unity for many of our applications, but some pieces are used in an unity application. All these applications are part of a big software architecture and are communicating over tcp/ip. When the visual studio solution is rebuilt, some of the produced dlls are copied in the unity plugins folder (about 40MB of c# dlls, and some c++ ones).
The problem is, for our developers, working on the unity application, each time some of these dlls are copied in the unity plugins folder, and unity get the focus back, the processing time is very long. Looking at the editor.log file we can especially see that the AssemblyUpdater.exe part take sometimes more than 1 minute.
One solution for us is to uncheck the 'auto refresh' preference option, but it's problematic since unity will never refresh and we need it for other resources.
Perhaps our workflow with unity is not the best, how can we address this issue ?
*.asmdef files or .dll 'auto-referenced' and 'v alidate' options don't seem to help on this issue.
ps: Using Unity 2018.4.9 on windows 10 (it seems it was a bit faster on unity 5)
Answer by matrem · Oct 23, 2019 at 08:39 AM
The unity command line : -disable-assembly-updater
can help
Your answer
![](https://koobas.hobune.stream/wayback/20220612213717im_/https://answers.unity.com/themes/thub/images/avi.jpg)