Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

JavaScript Libraries Not Published to Windows Azure

DZone's Guide to

JavaScript Libraries Not Published to Windows Azure

· Cloud Zone
Free Resource

Linkerd, the open source service mesh for cloud native applications. Get the complete guide to using Linkerd and Kubernetes to build scalable, resilient applications.

So late last year I was having trouble trying to figure out why a web site I’d been writing wasn’t working once published to Windows Azure.  I can’t remember which library it was (JQuery.UI perhaps), but once published I was getting a lot of broken JS calls (“can’t load library”, etc).

After a call with a friend today, he enlightened me about a problem which has been documented over on Stack Overflow – when using bundling with ASP.net (MVC or WebForms).  A release build (or production publish) publishes minified versions (“release mode”), but if a library doesn’t have a minified version, the script isignored altogether!

The solution would seem to be to create a second copy of the non-minified script and rename it to .min.js.  Let me know if this works (or doesn’t work) for you..

Original source:  (Stack Overflow) http://stackoverflow.com/questions/11980458/bundler-not-including-min-files

Linkerd, the open source service mesh for cloud native applications. Get the complete guide to using Linkerd and Kubernetes to build scalable, resilient applications.

Topics:

Published at DZone with permission of Rob Sanders, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}