11

Visual Studio 2017 is a disaster of epic proportions...

Comments
  • 1
    Why?
  • 1
    @gunoi It is constantly erroring out and crashing, it runs horribly slow on my machine compared to 2015, the new csproj format lost some incredibly useful features from the project.json format, and despite frequent updates none of these clear up.
  • 7
    Been on it for a while, no crashes at all... Performs better than 2015...
  • 0
    @mclark1129 I see. I didn't install it yet so I wouldn't know
  • 3
    I find vs2017 better than vs2015.
    I can put breakpoints in JavaScript and Chrome would obey them. Right from visual studio!
    It is not perfect though, crashes when I try to open one particular solution(there is a workaround for that); but that behaviour is inherited from vs2015. :/
  • 1
    Maybe i just need a wipe and reinstall of my entire machine. Its not just me though, a lot of devs in my office have complained if the same thing. I still miss project.json though, I think they lost a lot of great nuget features when switching to the new csproj.
  • 0
    @StefanH there's a tool on GitHub from Microsoft for removing various Visual Studio versions and dependancies here: https://github.com/Microsoft/...
  • 0
    @dontbeevil I'm not sure that's true. Opening a project.json project forces a one way upgrade of the project, and support for project.json is removed from any of the dotnet tooling going forward. The biggest thing I miss is that you could easily turn a nuget reference into a project reference with global.json. That and a few other things they've destroyed with the nuget experience.
  • 0
    @dontbeevil Mainly aspnet core projects.
  • 0
    I could not agree more I have used number of different IDEs but VS is the worst due to Microsoft's greed to make it look like it has lots of tooling, functionality... But most of them work 30-40% of time only.

    Pure integrations, pure design, pure performance, pure tooling, riddled with bugs, hanging all the time, keeping UI licked add it updates or refreshes something, lack of XAML tooling such as previewer, syntax checker, intelly sense... Btw, ask these exist, they just don't work, that's the Microsoft's way
  • 0
    @mclark1129 same experience, crappiest IDE
Add Comment