I’m working with my ASP.NET development team to try and create ‘better’ (i.e. cleaner) HTML when rendering pages. At the moment, .NET has a nasty tendency to do things like dump JavaScript into the page, making it a mandatory requirement on form controls and not allowing forms to work when JS isn’t available. In some instances, we’re struggling to overcome this without having to add a notable chunk to development time estimates.
I’ve worked with MVC before – via Struts in Java – and found that in that instance, I was able to keep HTML pages exactly as I’d wanted them to be. (This viewpoint is based on the ‘best case’ static HTML I typically developed beforehand, then handed over to the Java programmers to fill in the holes.)
This worked out really well and we were able to produce some of the ‘best’ web pages from a CMS that I’ve seen. Could .NET MVC give me the separation I need, or would it be a false economy to put aside valuable development time to test this?
If .NET MVC isn’t going to give me this fine-grained control over separation, any recommendations for .NET coding practices, libraries, etc. which might would be really helpful.
The ASP.NET MVC Framework would give you a much more familiar separation. Because there is no viewstate, etc in the MVC Framework you won’t have to worry about JavaScript being dumped into your pages. The only JavaScript calls you see will be ones that you manually add.
You can, for the most part, separate HTML / CSS / JS like you would in a different framework.