Hi Guys,
I have a question to you. Do you think that as SharePoint developer I should learn MVC? I know that for example SharePoint apps can be created with MVC, but also I can use ASP.NET. SharePoint stack has been build with ASP.NET. Do you think that Microsoft make a move to MVC? Or It’s a waste of time and I should stay with ASP.NET?
Thanks
Tomasz
I was an ASP.NET Developer and MVP before catching the SharePoint bug. SharePoint is an amazing platform. However, ASP.NET and web development continued to evolve past ASP.NET Forms, the post back model, view state, etc. SharePoint still holds on to much legacy ASP.NET. With that App Model we’ve come full circle and us SharePoint devs are playing catch up. MVC is not magic. It’s a UI Pattern. Learning ASP.NET MVC, WEB API, and JavaScript frameworks such as AngularJS will make you a better developer and more marketable.
MVC development is also part of the SharePoint certification path. Â Whether or not you decide to certify, it’s a good indicator of what you should be learning.
MVC is beneficial when you have a client with web with large relational data, you can surface all that using SharePoint-Provider app. Otherwise SP is quite potent to suit the needs of day to day intranet and more .Â
One other point to consider with MVC. A lot of Javascript Frameworks use MVC* type systems. So even Javascript: e.g. Knockout, Backbone, Node,
So the industry is going in that direction.
Hi Tomasz,
I am a SharePoint developer and I got thrown into a MVC solution last year. Prior to the MVC project I only developed Farm based solutions. The MVC knowledge  I gained was definitely not wasted when it came to SharePoint Apps.
I built on from this sample
http://www.asp.net/mvc/tutorials/mvc-4/getting-started-with-aspnet-mvc4/intro-to-aspnet-mvc-4
And then based my solution on this project set-up
http://efmvc.codeplex.com/
Have fun!
Luke
