Install SharePoint Server on the SharePoint servers.Ĭreate and configure the SharePoint farm.Ĭomplete post-deployment tasks as required. Install the SharePoint Server prerequisites on SharePoint servers. Install the required software updates on all servers that will be part of the farm. The basic steps in this deployment are as follows:Įnsure that you have done all the planning and preparatory work, such as verifying hardware and software requirements. While the farm configuration is not complex, it provides a fundamental infrastructure to implement a SharePoint Server solution on similar - or more complex farms. The deployment sequence and configurations that are described in this article are based on recommended best practices. NET Framework and use C# and Visual Basic to interact with SharePoint objects.Ĭompare SharePoint solutions with SharePoint add-ins.APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365 Also, when you build a SharePoint solution, you can leverage the. However, solutions provide deeper access to SharePoint objects. Administrators must install them, and because solutions execute in SharePoint, they can affect the performance of the server. SharePoint solutions require on-premises SharePoint farm servers. This VSTO add-in adds Ribbon controls, a custom task pane, and a dialog box to PowerPoint.Ĭompare the different ways in which you can extend Office, and decide whether you should use a VSTO add-in or an Office add-in.Ĭreate a SharePoint solution to target SharePoint Foundation 2010 and SharePoint Server 2010, or to extend SharePoint 2013 and SharePoint 2016 in ways beyond what's possible with a SharePoint add-in. Here's an example what a VSTO add-in can do. NET Framework and use C# and Visual Basic to interact with Office objects. For example, it can add tabs and controls to the Office Ribbon and perform advanced automation tasks such as merging documents or modifying charts. However, your VSTO add-in can be integrated more closely with Office. Users have to install VSTO add-ins, so they're typically more difficult to deploy and support. SharePoint Add-ins compared with SharePoint solutionsĬhoose whether to build a SharePoint add-in or a SharePoint solution.ĭecide between SharePoint Add-ins and SharePoint solutionsĬreate a VSTO add-in to target Office 2007 or Office 2010, or to extend Office 2013 and Office 2016 beyond what's possible with Office add-ins. Learn more about SharePoint add-ins, and then build one.Ĭompare add-ins for SharePoint with traditional SharePoint solutions. Here's an example of an app for SharePoint that helps users manage business contacts. Site owners can install, upgrade, and uninstall your add-in on their SharePoint sites without the help of a farm server or site collection administrator. You can also publish your add-in to users through an add-in catalog in SharePoint. You can sell your app for SharePoint in the Office Store. It's basically a small, easy-to-use, stand-alone application that solves a need for your users or business.
To extend SharePoint for your users, build a SharePoint add-in. Roadmap for Office Add-ins, VSTO, and VBA Learn more about Office add-ins, and then build one.Ĭompare the different ways in which you can extend Office, and decide whether you should use an app or an Office add-in. The following app for Office shows worksheet data in a Bing map. You can also publish your app to users through an app catalog in SharePoint, or on Exchange Server. The Office Store makes it easy to monetize your add-ins, manage updates, and track telemetry. You can sell your app in the Office Store. Your app can add functionality to documents, worksheets, email messages, appointments, presentations, and projects. It's basically a webpage that's hosted in an Office application such as Excel, Word, Outlook, and PowerPoint. To extend the functionality of Office, build an Office add-in. To get started, use the Office Developer Tools in Visual Studio, which lets you create projects, write code, and run your add-ins in a browser. These add-ins have small footprints compared to VSTO add-ins and solutions, and you can build them by using almost any web programming technology such as HTML5, JavaScript, CSS3, and XML. These add-ins can run in Office or SharePoint Online, and users can interact with them from many devices.įind out how to use the new Office Add-in model to extend the Office experience for your users. Office 2013 and SharePoint 2013 introduce a new add-in model that helps you build, distribute, and monetize add-ins that extend Office and SharePoint. NET Framework-based solution that users install on a computer. You can extend Microsoft Office and SharePoint by creating a lightweight app or add-in that users download from the Office Store or an organizational catalog, or by creating a.