I'm working in some WinForms C #, but now a Web application in .NET (C # is moving forward to developing front-end)). I have experience developing Rails on Rails (and a little bit with JSP pages and struts mvc) web applications.
Should I Jump Straight to the MVC Framework? (As opposed to going to ASP.Net) it is from the point of view of the future direction of Microsoft & amp;
Or if you want, my experience has been given as per date, what are the benefits for me for MSc vs. ASP.net?
Thanks
If you really need to work close to the wire MVC is a great choice. I mean, if you need very tight control on the markup; While acheivable with WebForms; It is very easy with MVC, it will be common for those applications which are targeting a public (such as the Internet) audience which can be a better graphical experience, on the contrary, if you develop internal (eg intranet) business applications While the graphical presentation is not important, the webform has very powerful capabilities, which allow you to move faster Umti will. Do not misunderstand me, you may find the webform app really great, but you give up some control on the markup.
Very often the viewest comes in such a discussion. MVC will not have any viewstate, so the on-the-wire footprint will be very small, which translates the cost savings of speed and bandwidth to a point. On the negative side, MVC can be more painful than building state applications, on the contrary, webforms are taken by default and are more naturally more important. It is generally okay for internal applications, keep in mind that the viewstress does not have to send to the wire ... there are extensions that allow you to load in the local cache. I am not in favor of one another, but you should be aware of what each can do in this regard.
If the unit testing is important to you then MVC is also a better option, because it is also easy, it is fully active in the webform, but you need to correctly follow your code.
Security is not a major factor since establishment of iPrchinium and IIDTT frequency in the HTTP pipeline through the HTPP module, so either in that respect.
Another major factor in making your choice is related to your skills compared to your time ... if you work in a stateless manner or for standard web technologies (eg HTML, CSS, jquery, etc. ...) MVC will take you much more time to do the very basic things. He said, once in place it would probably be cleaner, smaller, more testable and faster. If you need to move fast enough then there is a lot you can do faster in the webform. Webform also does a lot in lifting heavy loads about markup, so you can go to ASP.NET.
I actually use both for various reasons, and MS has said that they plan to continue support and development for both the plans.