title: Bundling resources via bundle.config vs BundleConfig.cs in ASP.NET 4.5 WebForms
body: <p>Regarding ASP.NET 4.5's new System.Web.Optimization / Microsoft.AspNet.Web.Optimization:</p>
  
  <p>Can anyone explain the difference in the use of bundling resources using the <strong>BundleConfig.cs</strong> class file as opposed to the <strong>bundle.config</strong> xml file?</p>
  
  <p>I've seen some <a href="http://www.mikesdotnetting.com/Article/197/Optimising-ASP.NET-Web-Pages-Sites-Bundling-And-Minification">articles</a> showing bundling both js and css in BundleConfig.cs, while <a href="http://blogs.msdn.com/b/rickandy/archive/2012/08/14/adding-bundling-and-minification-to-web-forms.aspx">others</a> showing bundling js in BundleConfig.cs and css in bundle.config.</p>
  
  <p>I guess I don't understand #1) why you wouldn't just do them both one particular way for simplicity - and #2) why anyone would prefer to hard-code resources like that in a class file?  It seems like a much more dynamic approach to just put them in an xml file that can be changed on-the-fly if necessary.</p>
  
  <p>It seems like more articles actually lean toward using BundleConfig.cs than anything else.  Is there some particular pro or con that encourages this?</p>
  
  <p>Also, if there is any real documentation on System.Web.Optimization, I would love to know the location (because I sure can't find it).</p>
  
  <p>Thanks-</p>