Web Essentials - Bundle versioning

Question

I'm currently using Visual Studio Web Essentials in order to bundle and minify my CSS and JavaScript files.

At present I'm manually creating the bundles with a version number (e.g. mybundle-1.0.0.css) in order to avoid caching issues when pushed out to production. I'm also having to manually change the bundle files version number each time a change is made to the source.

Is there any sort of automatic versioning functionality in Web Essentials bundling that I may have overlooked?

The ideal workflow would be:

Developer updates a source file.
Web essentials updates the bundle automatically.
Web essentials increments the version number in the filename automatically.

Is this possible?

If not, I'd be happy to hear any suggestions for better developer workflows.

score 16 · Accepted Answer · edited Sep 07 '15 at 05:55

16

Web Essentials doesn't have any support for dynamic versioning. Instead, I always use a dynamic runtime feature to automatically append fingerprints to my JS and CSS references. This works better for me, because it is completely independent of any build process or tooling support, instead it just looks at the actual files for changes. So it's much more robust.

I just wrote it up in a blog post here

edited Sep 07 '15 at 05:55

MNasir

137
7

answered Jan 09 '13 at 21:26

Mads Kvist Kristensen

2,610
2
18
14

Thanks for this. I like your suggested alternative too. – Brett Postin Jan 10 '13 at 09:16
2

The link isn't quite right (anymore?) http://madskristensen.net/post/cache-busting-in-aspnet – CoreyH Jan 14 '14 at 19:33

Web Essentials - Bundle versioning

1 Answers1