[giancarlostoro]

Also as a result of developing VS Code they've made HUGE improvements to Visual Studio 2017. If anyone had been programming .NET Core with VS 2015 and switched to VS 2017 you know what I'm talking about. I went from waiting 12 seconds for my project to compile to blinking and Chrome is opening up. Of course you have to turn off their browser debugging integration, that thing just sucks up so much dev time if you're not using it at all.

[flukus]

My experience with 2017 has been the polar opposite. It runs glacially slow compared to the 2013 installation on the same machine. The startup time makes eclipse look lean and mean, it takes over a minute to start.

[giancarlostoro]

Weird... It takes less time to start up for me, and compiling .NET Core is quicker, it even told me ReSharper is slowing down startup time at one point and suggested I disable it. Also suggested I disabled another component on startup because it was taking longer to start VS as a result. I guess it may vary depending on system specs? Not sure. I run it both on my workstation at work and on a VM on my laptop and at my home desktop.

[Sacho]

Have you tried disabling package restore on open?

[flukus]

I'm talking about just to start the IDE with no project, opening a project is time on top of that.

I don't see how it would make a difference though, running "nuget restore" only takes a second or two.