The wonderful world of knowledge technologies

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 CS...

Recently one of my clients had some strange behavior on their production farm. Team sites no worries, but when they started using publishing sites things went bad. Suddenly unexpected access denieds were showing up, even users with full control webapp rights were not able to access the site. Mostly when checking out pages, or changing the navigation settings. Luckily we got a helpful hint: we should review the super user full control and super user read accounts for the object cache, as described on the following page: http://technet.microsoft.com/en-us/library/ff758656(v=office.15).aspx By default the users are as follows: Super User Full Control: the site’s System Account; Super User Read: NT Authority\Local Service. In a claims authentication application, this default Super User Read cannot be resolved, which automatically leads to an access denied for the object cache. Solution: As described in the page above. You can also use this excellent script of Stef van Hooijdonk da...