Now, after waiting for quite some time, we finally can implement the real solution for .Net <-> javascript conversion and bridge the impedance gap in the projects that heavily rely on the powerful rich web UI.
Currently we have solutions like Script# and CofeeScript and others. The pros in cons of these systems have been discussed countless times (ex: Hanselminutes - JavaScript is Assembly Language for the Web: Semantic Markup is Dead! Clean vs. Machine-coded HTML).
With the recently released project Roslyn (or alternatively Mono Compiler Services) it is possible to have a clean solution to the problem: I write my data and data model in a language and an environment that allow solid validation and refactoring.
I’m ironing out some kinks in my implementation and, as soon as it’ll be in a stable state, I’m going to release a NWT (NeWT) project that will provide a similar to GWT (Google Web Toolkit) functionality.




