Setting up a development environment for BCS in SharePoint 2013

SharePoint 2013

Learn about setting up a development environment for developing SharePoint 2013 solutions and SharePoint Add-ins using Business Connectivity Services (BCS).

Last modified: September 17, 2015

Applies to: SharePoint Server 2013

In this article
Building server-based solutions and SharePoint Add-ins
Building client-based solutions
Additional resources

You can create SharePoint 2013 solutions and SharePoint Add-ins by using BCS on a client computer or on a server computer, depending on the type of solution you are building.

Typically, the majority of BCS solutions and apps will be hosted in a server environment. These server solutions and apps provide the greatest amount of flexibility with all of the features of BCS in SharePoint 2013.

For server-based solutions, it is usually best to develop the solution on a local computer where SharePoint 2013 is installed and then, when the solution is built and tested, deploy it to the production server. You can install a development environment on either a host workstation or on one or more virtual computers that are running Windows Server 2008 Service Pack 2.

Setting up an environment to build SharePoint Add-ins

The environment that you use for developing apps with BCS is the same as for developing any SharePoint Add-in.

To learn how to install the components of a development environment, including the operating system, SharePoint 2013, Visual Studio 2012, and Office Developer Tools for Visual Studio 2012, follow the instructions in Set up a general development environment for SharePoint 2013.

Client-based solutions enable Office 2013 client applications to access the same external data that a SharePoint 2013 solution or SharePoint Add-in can. You can do this by implementing code using the BCS Client Cache. The client components communicate with BCS through client-side code and the client cache. This provides Office client applications with the rich data that is available to SharePoint through external content types.

Because these solutions don’t require code, you can use SharePoint Designer 2013 and Office 2013.