Understanding REST APIs in Office 365, SharePoint 2013 & Custom Development The REST APIs are very straightforward and easy to use and allow for a platform-agnostic development approach
A Deep-Dive of SharePoint 2013 & Office 365 Proven Development Strategies This blog post will cover the latest tools and technologies for performing custom development on SharePoint Server 2013 , Office 365, SharePoint Online and Microsoft Azure environments
Development Tools and Related Strategies for Public, Private, and Hybrid Environments There have been many improvements as well as options added to Visual Studio 2013 to address the new technology releases of SharePoint 2013 , Office 365 , SharePoint Online , and Microsoft Azure
You should always keep in mind SharePoint 2013’s “claims first” authentication architecture during your development as well as in discussions with the business about their custom requirements
APIs and Development Options for Data and Resources SharePoint 2013’s APIs allow apps, as well as other elements, to connect and integrate with SharePoint’s core features
Workflow Development "From the Consulting Trenches" There has been a complete update to SharePoint 2013 ’s workflow capabilities and overall workflow architecture, as shown in image below, with new features as well as the underlying workflow engine itself receiving a major overhaul. In this post, EPC Group's SharePoint and Office 365 hybrid development team will walk you through new best practices and strategies regarding workflow development. The workflows in SharePoint 2013 run within Workflow Manager by services, processes and logic received from SharePoint 2013
So you have a very good and well established SharePoint application and all is going well but it is now 2013 and Microsoft have done again; they have gone out and release yet another version of Microsoft SharePoint which is SharePoint 2013
” When Configuring SharePoint 2013 My Sites SharePoint 2013 My Sites are hosted by a web application and rely on a User Profile service application
I was a little bummed after playing with 2013 for a week now to see that the ECM functionality is not substantially changed...I did several tests of importing 2010 taxonomies into 2013 and it worked like a charm!
Our consultants may be onsite at any given client and require access to a document off of our SharePoint Server 2013 intranet or ECM platform that a client requests and we must be able to immediate to meet that request
Should I Prepare for a Hybrid SharePoint Platform In Part 1 of this white paper , we discussed some of the core differences around SharePoint 2013 on-premises (private cloud) vs. the hosted (“public cloud) as well as a hybrid SharePoint 2013 deployment which allows for a middle ground for you to tailor based on specific requirements, concerns, security requirements, as well as custom development strategies
no search term matches found in comments.