Future of the Microsoft ASP.NET Web Optimization Framework

Sep 7, 2014 at 8:04 AM
Now a lot of talk about what the Microsoft ASP.NET Web Optimization Framework will go into history and instead will need to use the Grunt tasks (https://github.com/aspnet/KRuntime/issues/238 and https://github.com/aspnet/Home/issues/134).

I would like to hear comments from Web Optimization's team.
Feb 26, 2015 at 10:03 AM
I would like to hear comments from them as well.
However, since Microsoft has moved all of it's stuff over to GitHub, I think that there might be more response on the ASP GitHub issue board https://github.com/aspnet/home/issues
I posted in a issue here https://github.com/aspnet/Home/issues/156
:-)
May 15, 2015 at 10:39 AM
Now it became clear, that in ASP.NET 5 and ASP.NET MVC 6 will not support of this library. Microsoft recommends switch to Grunt or Gulp. In addition, in ASP.NET MVC 6 was created special Tag Helpers, which allow to include optimized files to the view. More information about these Tag Helpers can be found in Dave Paquette's articles: “Web Optimization – Development and Production in ASP.NET MVC6” and “Link and Script Tag Helpers in MVC6”.