After some Unity (2018.2.21f) compile operations, working with Visual Studio 2017 Community (latest VsTools) becomes very tedious since intellisense starts to slow down till it’s totally unusable and I have to restart VS again.
TCP ports are open and I don’t use antivirus on Win10, therefore Unity-VS communication should be free.
Any advice or any way to debug this issue?
thx
i’ve noticed this also…
here is from slow capture (notice how long it takes to get logexception in the dropdown)
then restart vs and its fast (instant suggestions)
but then next time when you start the project, its slow again, until restart it seems?
It’s a known bug they said and it looks like it’s not gonna be fixed. Go for VS2019 like I did.
1 Like
nice, so vs19 works fine with older versions too (2017 at least) ? or i guess could keep both…
Yes it works but with Unity2017 the shortcut F5 is not set to attach to Editor so u have to manually go to: Debug>Attach Unity Debugger