regressions: VS glitches

Unity Engine
1

I acknowledging that, clearly, a lot of effort went into this VS build. It is much faster, well integrated with Unity and the amount of settings in the unity plugins are a nice touch.
But from the standpoint of usability, there is still work to be done because it is quite glitchy.

For example some times help>unity api documentation disappears (987740)
3353382--262420--devenv_2018-01-13_23-51-57.png
no toggle comment, it’s on or off, we need ctrl+/ of VS code
ctrl+w which i remapped to file>close won’t close a tab
ctrl+R which is remapped as rename, never works, even though it shows in the right click menu
(977739)
autocomplete can be sluggish at times and miss suggestions and forgets what was used before, also it seems to ignore context some times, I think anyone at UT who used monodev and switches to VS can clarify what I mean
(987741)

2

Hi

We investigated with Unity this case where Unity 2018 beta was not properly delegating to VSTU the generation of solution and project files. Because of this, you ended up with a regular C# solution so all VSTU features regarding debugging, wizards, reloading, API documentation, etc… were disabled/hidden in VS.

It was a registration issue, that was just fixed in Unity beta. We also patched VSTU to be more resilient about those issues.

We expect the fix to be soon available in Unity beta.

Regards
Sebastien Lebreton [MSFT]

2 Likes
3

Thanks Sebatien, great to hear the team is backing us up.