Closed MisterJames closed 11 years ago
right on.. Thanks
No worries :)
I wasn't sure what to do with the Nuget versioning though, I assumed you'd update the numbers before you pushed the package?
the build server assigns the version numbers, after I test a release candidate from the myget feed I just push that set of packages to the public feed
Eric Hexter
blog | http://Hex.LosTechies.com info | http://www.linkedin.com/in/erichexter
On Tue, Jan 29, 2013 at 9:11 PM, James Chambers notifications@github.comwrote:
No worries :)
I wasn't sure what to do with the Nuget versioning though, I assumed you'd update the numbers before you pushed the package?
— Reply to this email directly or view it on GitHubhttps://github.com/erichexter/twitter.bootstrap.mvc/pull/60#issuecomment-12872057.
Ah, sweet deal. Thanks :)
Addressed an issue where the jQuery source map file on IE10, running on Win 8 with Visual Studio 2012, was causing an issue in the minification/client script delivery pipe, resulting in critical JavaScript errors being thrown from the browser.
The fix was two-fold. First, I switched the jQuery bundle to use the semantic version tag. Second, I added jQuery.Migrate to the package dependencies and added it to the bundle config.
Details on the error here: http://jameschambers.com/2013/01/jquery-script-map-causing-critical-error-in-jquery-1-9-0/
...and here: http://jameschambers.com/2013/01/upgrading-to-jquery-1-9-0-starts-giving-you-unhandled-exception-errors/