You can deploy Office solutions developed with Visual Studio Tools for Office in several ways.In this thread, find conceptual information to help you decide how to deploy your Office solutions and sample code to help explain the steps.
The methods available to you depend on the versions of Visual Studio and Microsoft Office that you are using. This post has information about deploying with Windows Installer (MSI) and ClickOnce. In addition, there is troubleshooting information about deploying the Office primary interop assemblies (PIAs).
Applicable versions
|
VSTO runtime |
Visual Studio |
Office |
.NET Framework |
|
VSTO 2005 SE |
Visual Studio 2005 |
2003 |
2.0 |
|
VSTO 2005 SE |
Visual Studio 2005 |
2007 |
2.0 |
|
VSTO 2005 SE |
Visual Studio 2008 |
2003 |
2.0, 3.5 |
Windows Installer: Use this method to create additional registry keys and brand your installer.
Office Primary Interop Assemblies
MSDN Library
=====================================================================================
Applicable versions
|
VSTO runtime |
Visual Studio |
Office |
.NET Framework |
|
VSTO 3.0 |
Visual Studio 2008 |
2007 |
3.5 |
|
VSTO 3.0 SP1 |
Visual Studio 2008 SP1 |
2007 |
3.5 SP1 |
ClickOnce: Use this method to create and install self-updating applications.
Windows Installer: Use this method to create additional registry keys and brand your installer.
Office Primary Interop Assemblies
MSDN Library
=====================================================================================
Deployment blogs from the VSTO team