The future of .NET in conjunction with SharePoint

With the introduction of the app model and the further expansion of the client-side object model, the classic SharePoint .NET components look like to get the status of deprecation.

What would be the best way for Microsoft to keep enabling developers to develop fullblown SharePoint portals? Should they continue the ASP.NET framework and the tight integration with the SharePoint platform? Or should they introduce a new web development framework for SharePoint portal development?

In its current state Microsoft needs to do something, as developers are now confronted with two models they need to support: the tighly integrated SharePoint .NET platform which a rich set of components on the one hand, and an agnostic CSOM based world with little standardization on the other hand.

My bet is that the classic platform will be downsized, keeping only the essential core components, and around this core a new set of standard Html5/JavaScript and .NET based tooling will arise, fully based on a rich CSOM.

So, what do you think?

Cross-posted on


Populaire posts van deze blog

Troubleshooting restoring a site collection

WhatsApp integration with your CRM system

TypeScript async/await example for the browser