Search Wiki:
You can develop a Visual Studio 2010 Tools for Office solution for the 2007 Microsoft Office System and Microsoft Office 2010, and deploy the solution by using a Visual Studio 2010 Setup project to create a Windows Installer package. You must still use ClickOnce to secure your solution, but you can use the MSI to distribute your files to end user computers.

The default publishing option in Visual Studio Tools for Office is ClickOnce. You can use ClickOnce to create and install self-updating applications with minimal user interaction. However, you must use Windows Installer to deploy application-level add-ins to All Users. Windows Installer allows you to configure the deployment in great detail, but this does require more effort to configure correctly.

There is a whitepaper that describes how you can use these code samples: http://msdn.microsoft.com/en-us/library/ff937654.aspx.

The folowing list of projects demonstrate how you can integrate these into your solution to deploy with a Windows Installer file.

.NET Framework 4 Projects
    1. Addin Deployment (Single + All User)
    2. AddIn Deployment – All User Install for 64-bit Office
    3. Document Deployment - VB Version of Serverdocument Custom Action to copy and customize the document
    4. Document Deployment - CS Version of Serverdocument Custom Action to copy and customize the document
.NET Framework 3.5 Projects
    1. Addin Deployment (Single + All User)
    2. AddIn Deployment – All User Install for 64-bit Office
    3. Document Deployment - VB Version of Serverdocument Custom Action to copy and customize the document
    4. Document Deployment - CS Version of Serverdocument Custom Action to copy and customize the document
Last edited Oct 6 2010 at 11:00 PM  by maryrlee, version 7
Updating...
Page view tracker