2 ms·
I suspect the curse of backwards compatibility might cause a problem - there are so many systems that have dependencies on SharePoint (including a lot of Micros
by arethuza 13y ago
I suspect the curse of backwards compatibility might cause a problem - there are so many systems that have dependencies on SharePoint (including a lot of Microsoft's own products). I found this page the other day which talks about the non-trivial process of picking the right API for talking to SharePoint:
http://msdn.microsoft.com/en-us/library/office/jj164060%28v=office.15%29.aspx http://msdn.microsoft.com/en-us/library/office/jj164060%28v=...
The diagram trying to explain how the different APIs relate is a pretty good visualization of the problems that anyone trying to refactor SharePoint would face.
- jamin 13y agoIt is widely known that 2013 will be the last version of SharePoint. Everything will be an incremental upgrade from now on with customisations decoupled from SharePoint through 'Apps' working off web services.
- uberb00t 13y agoAt SharePoint Conference 2014 the product team specifically announced that there will be a SharePoint vNext released on-premises, released in the summer of 2015, presumably to be named SharePoint 2016. Apps are being pushed hard for all customizations so as to decouple code from the "core" of SharePoint so as to allow for a better upgrade strategy. That being said, I do see Yammer as replacing a lot of functionality within SharePoint over the next 2-3 years, but I believe SharePoint as a product (especially as it relates to document management and search) will continue to exist for at least another 4-5 years.