Developer’s Toolset for #SP2013 – Add MVC and mix in Razor!
The clear message from Microsoft for SharePoint 2013 development is a move to the app model. Here’s an introduction: http://msdn.microsoft.com/en-us/library/jj164084.aspx. SharePoint 2013 apps moves your code assemblies out of the SharePoint platform and into separate web applications. There are two reason for this:
1. A requirement for a more stable SharePoint platform. If you’re running SharePoint across your organization you don’t want badly written applications impacting reliability.
2. In Office 365 you can only add assemblies in sandboxed solutions. However, because of the very constrained subset of the SharePoint API available to such solutions their functionality is limited. Now, Office 365 will use functionality provided by SharePoint apps.
The move to SharePoint 2013 brings SharePoint 2013 developers fully back into the ASP.NET development fold. In particular, MVC with Razor greatly simplifies web application development. You will be using the SharePoint Client Object Model to access SharePoint objects from your app.
Here are some links that help you get started with building SharePoint 2013 apps:
- How to: Create high-trust apps for SharePoint 2013 using the server-to-server protocol: http://msdn.microsoft.com/en-us/library/office/apps/fp179901. Essential for building on-premise SharePoint 2013 apps.
- Building ASP.NET MVC Based SharePoint Cloud Apps: http://www.ilovesharepoint.com/2012/07/building-aspnet-mvc-based-sharepoint.html. A number of steps in this guide are automatically performed with Visual Studio 2012 released version.
- ASP.NET MVC 4: http://www.asp.net/mvc/tutorials/mvc-4. An excellent introduction to get you up to speed with ASP.NET MVC with Razor.