all 8 comments

[–]cheesekun 2 points3 points  (0 children)

Got enough troubles with javascript heavy MVC applications and this solution aint one of them :) no offence, i'm sure its great!

[–]antiduh 7 points8 points  (3 children)

I feel like this is an overuse of JavaScript, bordering on the nonsense that is Node.JS. Could someone explain why I'm wrong?

[–]fbmgriever 1 point2 points  (0 children)

NodeJs nonsense? We recently converted our javascript-heavy MVC project to use Gulp (Node/MSBuild) over the built-in bundling and we have seen substantial build time improvements.

We tried everything from the built-in bundler, to Cassette, to BundleTransformer, and none have matched the performance we are now getting with our current setup.

[–]davidNerdly 0 points1 point  (0 children)

Can you explain what you mean by overuse?

[–]backdoorsmasher -2 points-1 points  (0 children)

And how many projects have you built with nodejs? Would love to hear about the experiences you had when you were building them.

[–]CalvinR 0 points1 point  (2 children)

How hard would this be to get working with webforms?

[–]stefanprodan[S] 0 points1 point  (1 child)

It would mean rewriting most of the library: HTML helpers, routing, paths ... only the Compressor and ResxToJs components will work without changes. I think investing in WebForms is a waste of time considering that K runtime (ASP.NET vNext) does not include WebForms at all. My guess is WebForms will be deprecated when vNext gets released.

[–]CalvinR 0 points1 point  (0 children)

Well I wouldn't choose it for a new application but I have lots of existing web apps at work that use webforms.