@Sunil Unnithan: no - need to look at adding this header. The plan going forward is that we'll provide you the ability to control much more about the response message from within your transform than we do today.
My main technology passions include pretty much anything on language theory, agile development, and service-oriented architecture.
@DotnetShadow: We renamed the package Microsoft.Web.Optimization to Microsoft.AspNet.Web.Optimization - that's why those 2 different packages exist. When we released the later version of Microsoft.AspNet.Web.Optimization, we also updated the Microsoft.Web.Optimization package version such that it contained no actual content - just a dependency to the renamed package. As such, it basically acts like a redirect.
For the different versions of Microsoft.AspNet.Web.Optimization, we follow the conventions outlined in the Semantic Versioning specification (http://semver.org). Therefore, we published a couple different pre-release versions and recently the first stable version (1.0.0).
The CDN feature is available in 1.0.0 (http://nuget.org/packages/Microsoft.AspNet.Web.Optimization/1.0.0) - I had put some code on my blog that referenced this code before we had pushed the final package to nuget.org. Sorry for the confusion there.
Hi Sunil - yes, it's not pretty, but you should be able to use just the version stamping piece by doing 3 things:
- create a custom IBundleTransform which does nothing other than sets the media type - we actually have this in the fx (look at the NoTransform class in reflector), but unfortunately it's internal
- create and register the bundle in BundleConfig
We'll also look into making more modular support easier in future versions. Hope this helps.