System.Web.Optimization.Bundle vs. WebEssentials

Question

What is the difference between System.Web.Optimization.Bundle and the binding operation in the Visual Studio WebEssentials plugin?
I mean not only the final result, which should be almost the same, but also internal, especially. differences (if any) in debug and release mode.
And finally, what will I get and what am I missing when choosing this or that?

Answer 1

As you know, System.Web.Optimization.Bundle is mainly used to link js or css files to reduce page size or loading problems, but Web Essentials is a collection of (mostly) Internet-related enhancements to Visual Studio. It includes many new IntelliSense add-ons (especially for CSS), new BrowserLink features, automatic JSHint for Javascript files, new warnings for HTML and CSS, and many other features. Any web feature you want to add should probably be here.

In details, if you want to check that the links below may be useful.

• For consolidation and reorganization https://docs.microsoft.com/en-us/aspnet/mvc/overview/performance/bundling-and-minification

• For Web Essential https://blogs.msdn.microsoft.com/mvpawardprogram/2013/11/05/making-web-development-wonderful-again-with-web-essentials/

Answer 2

I use both approaches from time to time. The result is almost the same (size of output files, compilation time, etc.).

• System.Web.Optimization . You support functionality through * .cs and * .cshtml files.

• Web Essentials . You support functionality through the context menu and configuration stored in .json (xml) files.

But you cannot use the System.Web.Optimization approach if you are developing a static html page (actually not on the server side)