I was ok with dropping monodev when I saw that vs 17 was fast and that sweet live error detection but even the editing doesn’t work well.
In general when something doesn’t work, you don’t phase out what works, you do a transition across month until there is feature parity.
I hope the current frustration gets rewarded with proper support and all this gets fixed long before the end of this beta cycle because the rest of 18.1 is so full of sweetness.
I logged a bug for this nasty one 989527.
You want to know another shitty bug that has been in since VS2017 came out and not fixed ever…
Select a line or some, then cut/copy, then shift+delete twice … notice when you come to paste what you thought was moved into the clipboard earlier, before using shift+delete on those selected line(s) … no longer exists… you just paste empty lines.
It has gotten me multiple times in the past, as I use the shortcut to wipe out entire lines where I swear I had copied the code before doing so. Dumb bugs… ontop startup bloat, and a really shit solution explorer and even more shit the assembly browser… yeh I don’t miss monodev for much, but surprisingly it did somethings better.
VS2017 - the Sweaty copy buffer eater
Good thing Undo works, I know because I used it a lot, now.
(Did you log a bug on the unity reporter? It’ll help them)
Hi @laurentlavigne . Seb from the VSTU team here.
I filled an issue regarding auto-complete:
Regards
Sebastien Lebreton [MSFT]
I didn’t… wasn’t really a Unity bug… should though… I could do with winning a coffee mug 
They work very closely with microsoft and seem to be taking responsibility for the transition, which is great, so filing a bug with Unity seems to be the best route.