ASP.NET MVC vs. Webforms: Replacing WebForms Controls -


I have read many more posts here, so I get views on Pro vs. Opposition, especially with full control over them ( MVC).

My question is in relation to UI controls: In MVC, I have to write all my UI controls (or HTML equivalent). Now it will not be difficult? Due to these third-party vendors due to the fact that it is difficult to write UI control for ASP.NET itself, and is capable of targeting all web browsers, and also that we are able to control UI controls It's better to focus your time on business logic rather than spending a lot of time writing HTML code.

I understand that this feature gives us complete control over the final HTML, but it is not counter-productive to do it yourself if it was so easy to write to myself, then this 3- How are all vendors of RD Party now living? We could do all this with webform days of all these years.

I'm sure I'm missing something here or a little stupid, but please tell me about what I'm missing in a specific relationship. Write the UI bit automatically Used to be.

Just because I get the full control of the program by writing the IL code, do we go and do this? We still use things like C # and so - the principle of "keeping complete control over HTML" - I have not bought it in that idea.

Please help to get my head around this UI bit. Other things I think, TDD based development is possible with the separation of anxiety, MDC etc. But why do I go around writing UI controls myself - this is a little work, right?

The thing is:

If you master the web development If you want, you have to master the HTML + CSS + Javascript

and WebForms with WebForms is the way to learn how to do it, but with power with MVC the power of the net HTML + CSS + is to generate javascript you want


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -