There's a pretty spectacular example a DurandalJS based, ASP.NET MVC 5 backed SPA over at:
https://durandalauth.azurewebsites.net/
There's a problem with it, though, is the Weyland powered optimization fails for Visual Studio's Post-Build events with a message like the below
Which is strange because the post build event is this:
cd $(ProjectDir)
weyland build
Which when executed from the command line works just fine:
Why would this be? I've search all over the net and all I keep finding are references to a similar but (perhaps) an unrelated problem where an additional line of the config
"insertRequire: ['main'],"
[EDIT]
I'm using Visual Studio 2013 Pro Update 2, no plugins.
I've git clone'd the latest project from DurandalAuth on GitHub using this url:
git clone https://github.com/yagopv/DurandalAuth.git
You can see the project here: https://github.com/yagopv/durandalauth
I'm using this in my post-build event in visual studio:
cd $(ProjectDir)
weyland build
My output from my build can be found at this pastebin: http://pastebin.com/ezpTEPk7
Everything I'm doing has zero modifications from the original project as seen from a Git Clone.
When you look at your build output you'll find several lines like
You'll also find lines like
While these are not showstoppers regarding to execution they cause the build to return fail.
This is why Visual Studio reports a failed build.
EDIT
I did some major cleanup using ReSharper.
To completely ignore your .js files - you could remove .task.jshint from the weyland-config.js
Also to mention is the fact that your main-built.js does not get uglified with shipped weyland-config.js
In the first .task.uglify add an exclude for the App/mail-built.js and add a new .task.uglify as the last task. This path to main-built.js must be prepended with ../ since the path is relative to build folder.
Also found issues in when debug=false in web.config Haven't resolved that yet.
My weyland-config.js looks like this: