Question by Graybad1 · Feb 27, 2018 at 10:54 PM · scripting problem visual studio visualstudio

Is there a way to prevent this weird project and solution generation done by Unity when using asmdef files?

Can someone please help me with this? It's making it near impossible to use Unity with VS.

There also is no noticeable pattern in when it happens, ie can happen when creating, saving, or loading a file. It can even just happen at random times such as when I'm AFK and have Unity/VS open. StackOverflow Link

Add comment · Show 3

meat5000 ♦ · Feb 27, 2018 at 11:47 PM 0

Does this happen when Editor Attaching is not enabled? Also, read this thread, which speaks of the need to link references and define Editor Assemblies. Perhaps if its not linked it may be seen as separate and the reason why VS is trying to throw it in to a new project.

Graybad1 meat5000 ♦ · Feb 27, 2018 at 11:55 PM 0

I have tried with Editor Attaching enabled and disabled, it makes no difference. Also, everything is defined and linked perfectly. It works fine 95% of the time and the project can always build even if this happens, it's just annoying when it does.

I have also switched over the VS Code as it doesn't use the csproj/sln files.

meat5000 ♦ Graybad1 · Feb 28, 2018 at 09:31 AM 0

https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/2463093-stop-automatically-messing-with-my-solution-config

Sorry this link wont solve it but helps outline the issue. It seems to be more VS related than Unity. I'm guessing it seems random because of the way your Focused/Backgrounded programs respond. The example is Unity not recompiling code until you click the window. Perhaps VS is the same in that its not showing you what its doing until its given some priority making it hard to track down the Root. Do you have an Editor folder inside your Assets folder or something strange like that?