@EdCharbeneau Bower is still used for client-side dependencies in the project templates. NuGet is not being used for it and won't be in the future.
|Coffeehouse||HTML 5 Output Tag Does Not Work In IE 10!||13||Mar 21, 2013 at 8:14AM|
The NUglify package that BundlerMinifier uses is a .NET Core port of AjaxMIn. It is being actively developed whereas AjaxMin isn't.
@BraveStar, all the Gulp, Grunt and npm tooling in Visual Studio isn't going anywhere. In fact we keep investing in it and you'll see more features coming live in the next release. All the extensions for Task Runner Explorer for Webpack, Broccoli, Brunch etc. will continue to work and receive updates. It doesn't use Gulp/node under the hood because it doesn't have to in order to bundle and minify. Otherwise it would have.
If you want to go above and beyond what BundlerMinifier offers, then using Gulp or Webpack is a great choice still.
I would encourage you to check out the BundlerMinifier wiki for more details that will shed some light on what this is.
Remember, Gulp support isn't going anywhere and is fully supported in Visual Studio now and in the future.
175x175 and 90x90 pixels are the sizes optimized for the Visual Studio Gallery website and not the Extensions and Updates... dialog. I've raised the issue with the extensibility team to unify the image representations so we can optimize for both locations. My reasoning for optimizing for the Gallery over the Extensions and Updates dialog is that people use the Gallery to browse for new interesting extensions and use the dialog when they already know what they want. So the Gallery is much more a place where you need your extension to look good
@OzBobWa, Web Essentials 2015 has this exact feature that adds Grunt and Bower to any web project. Just right-click the project node in Solution Explorer and go to Add... -> Grunt and Bower.
You should be able to use the Package Manager Console to execute yo commands. We'll also add a Open PowerShell Here feature to the Task Runner Explorer to make it easy to get to Powershell at the right path.
JSX support is coming, but we haven't started on it yet. We've done the initial architecture and know how to add the support, now we just need some time to implement it. I can't make any guarantees that it will make it in to VS2015 RTM, but I hope it will.
You can open folder based websites by doing File -> Open Website. It's a directory based project system that doesn't require any project files.
Visual Studio 2013 Update 4 does not include the Task Runner Explorer nor the Package Intellisense extension. They are separate downloads you manually have to install.
We haven't implemented that yet, but it's on the backlog to add support for binding to all the VS configuration.
The extension now supports Visual Studio 2012