To get started, I think you will find all in one pretty well. But over time, if your site has a certain degree of complexity, I think you might find that you want more control.
For example, I use some JS files that cannot be reduced due to the javascript format inside it (note that this is a third-party file that I do not want to modify). Therefore, control over what is being โprocessedโ is extremely important.
In another case, we use, as a rule, to combine our JS files with the help of a script manager that creates ashx pages. As far as I know, this is not all โall in one solutionโ. In addition, the script manager is already changing the headers according to the cache settings that I configure for it.
Another example of compression is that if you have a lot of traffic depending on the type and size of the separated content, you want to use different compression levels. I think I remember the post by Jeff Atwood saying that they went through for SO and that they needed a lot of control over the compression.
Another example is caching. Feature, if you want to get into the caching of donuts or donuts, it has nothing to do with IIS and all about how everyone can cache different parts of the page - for example, it can cache the main page, but not the dynamic content of the page itself ... afaik no 'all in one solutions' satisfies this.
In general, I generally think that I need more control over what is happening, and I prefer that some kind of minimization occurs during the build process (as you know exactly what you get when you ever launch your application ) Compression happens at the IIS level, but I like to manage it at the APP level. Any cases for caching or compression I just manage through a web configuration that allows a lot of control. Therefore, I think everything goes in one, if you have something simple, but if you need more control, you still have to do it in the application.
Hope this helps.
UPDATE:
Just thought that installing all these things at the application level is very simple if you use ASP.net MVC, but in classic ASP.net it can be a lot harder to combine headers, etc. Therefore, in some cases, if you are dealing with an old application using classic ASP.net, it may be easier to use all in one solution.