Deployment Overview (Office Development in Visual Studio)
You can use ClickOnce or Windows Installer deployment technologies in Visual Studio to publish your Office solutions by using Microsoft Office SharePoint Server, a network file share, or an installation disc. For advanced scenarios, you can create your own custom installer.
Applies to: The information in this topic applies to document-level projects and application-level projects for Microsoft Office 2010 and the 2007 Microsoft Office system. For more information, see Features Available by Office Application and Project Type.
You can use ClickOnce to publish solutions, install prerequisites, configure security, and provide automatic updates. For more information, see Publishing Office Solutions by Using ClickOnce and How to: Publish an Office Solution by Using ClickOnce.
ClickOnce deployments can be customized to publish referenced assemblies or data files. For more information, see How to: Publish Referenced Assemblies and How to: Publish Data Files in a ClickOnce Installer.
You can publish your Office solutions by using a Setup project to create a Windows Installer file (.msi). You must use the ClickOnce security model for Office solutions to secure your solutions, rather than using a Code Access Security Policy script as Visual Studio 2005 required. For more information, see Publishing an Office Solution by Using Windows Installer.
You can use a SharePoint document library to publish customized documents. For more information, see How to: Publish a Document-Level Office Solution to a SharePoint Server.
There are several ways for users to install Office solutions: by running the Setup program, by opening the deployment manifest file, or by opening the customized document or workbook. For more information, see How to: Install a ClickOnce Office Solution.
Office solutions show up in the list of installed programs, so they can be uninstalled by using built-in Windows functionality. For more information, see How to: Uninstall a ClickOnce Office Solution.