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 . EPC Group highly recommends that your organization’s developers have both on-premises and cloud development environment tools available so that they can become familiar with them, and also ensure that compatibility of a future architecture, as shown in the image below, is taken into consideration. Visual Studio 2013 and Related Tools and SDK Visual Studio 2013 is the enterprise development tool that should be used on almost any development initiative because the application life-cycle management as well as code repository integration and new SharePoint 2013 integration features make it the only tool available on the market with its capabilities
Security & Identity Management "From the Consulting Trenches" There are a number of security, identity management and authentication considerations when developing custom applications and related features in 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
SharePoint Deployment Introduction Deployment is required to take a SharePoint Customization or Development Solution and put it on a server. Development and deployment in SharePoint is different from development in .NET (ASP.NET, Silverlight etc)
1 Comment - no search term matches found in comments.
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 following is a SharePoint 2010 Web Standards and Usability Quick Reference Guide following EPC Group’s best practices for SharePoint GUI development (master page) and configuration best practices
If SharePoint is to be able to meet these requirements customization or third party Records Management solutions are needed
SharePoint truly is self-service once you’ve done extensive planning, configured the platform, implemented a governance strategy, created a taxonomy, organized, identified and imported all of the content, built the necessary forms and workflows, done a few customizations, and so on. In order to do these things correctly, and to ensure adoption, an organization has to possess a broad array of skills that fall into the following categories: IT Pro Information Architecture Software Development Evangelist & Trainer The IT Pro’s job is to set up and configure the platform which requires, at a minimum, a firm understanding of hardware, virtualization, Windows Server, IIS, Active Directory, SQL Server and SharePoint (configuration and administration)
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. The development team at EPC Group uses APIs, as shown in the image below, that provide apps their ability to view content or integrate with a workflow or even perform searches