[rajeemcariazo]

In my experience, Visual Studio 2013 is better than Visual Studio 2015 when working on ASP.NET. I get many errors in Razor files when on VS2015. All errors disappear when I clean and rebuild the whole project. I hope it gets better on the next version of Visual Studio.

[wvenable]

I also found in some cases certain design-time errors go away by closing and re-opening Visual Studio. I used to pull my hair out trying to fix those errors; now if I get an error I don't understand it's a clean/rebuild cycle first and a close/reopen second.

I kind of feel VS is getting less stable as Microsoft embraces the packages-for-everything style that is pervasive in web development.

[jmkni]

For VS 2013, there where a lot of great extensions for VS designed to improve the front end web development experience (ie. things like LESS, SASS, Typescript) and also nuget for managing client side JS/CSS libraries.

These became deprecated when 2015 rolled around, as the advice became to use more industry standard tools (node, gulp, grunt, etc) to accomplish the same tasks.

I understand the rationale, and use those tools now, but certain aspects are definitely more cumbersome now than they where a couple of years ago when you could just let VS take care of it.

[daigoba66]

Indeed. I think a lot of the ASP.NET tooling (particularly around Razor) was rewritten in Visual Studio 2015. There are ton of bugs and other annoyances (for example: https://github.com/aspnet/Tooling/issues/116).

[UK-AL]

Err how old is your version MVC your using. Could be they depreciated it?

[rajeemcariazo]

i use ASP.NET MVC 5