We are happy to announce availability of new #SharePoint Client Side Object Model (#CSOM) version targeted for the #Office 365 or more specifically for SharePoint and Project Online. This release again contains few updates on the existing SharePoint CSOM assemblies and some maintenance changes. These monthly changes are not significant, but we want to align on the monthly rythm in future, so that you can know beforehand that there will be new version arriving during end of each month. You can find the latest CSOM package for #SharePoint Online, including the Project Online CSOM assembly, from the NuGet gallery with an id of '#Microsoft.SharePointOnline.CSOM'. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. We do recommend you to use the Nuget Package to gain
If you have been wondering about how big some of the changes coming to #SharePoint are, read this article. Its a really good read about how big of a change the new open #SharePoint Framework is. Don't forget that the framework was released in preview mode this past week as well You can read more about its release here.
So the new UX and visuals are great but naturally this raises a number of questions from a technical or developer perspective related to what’s going on “#under the hood.” How is this new experience put together codewise compared to the “old SharePoint?” If one makes the assumption that this is the direction that #Office 365 SharePoint is headed in the future — not just for #document libraries but for all other types of sites and pages — what impact