Tuesday, April 5, 2011

Deploy Office 2007 VSTO solution using Windows Installer

Using ClickOnce installation sometime can be quite cumbersome, especially when combing with document-level application and customized file type.

To simply the deployment, using windows installer project will definitely worth the effort.

namely, a few things that you might miss out:

> include project output then .vsto, .manifest seperately.
> add a custom action project (installer class) to update customization manifest (_AssemblyLocation), you need to use ServerDocument class to achieve this.
> append '|vstolocal' to the manifest location:

ServerDocument.AddCustomization(
targetLocation,
assemblyLocation,
SolutionID,
deploymentManifestLocation,
true,
out nonpublicCachedDataMembers);

references:
Deploying a Visual Studio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office System Using Windows Installer
http://msdn.microsoft.com/en-us/library/cc563937.aspx

Deploying an Office Solution by Using Windows Installer
http://msdn.microsoft.com/en-us/library/cc442767.aspx

How to: Attach Managed Code Extensions to Documents
http://msdn.microsoft.com/en-us/library/bb772091.aspx


How to: Create and Modify Custom Document Properties
http://msdn.microsoft.com/en-us/library/dhxe2d75.aspx

How to: Change the Installation Path of an Office Solution
http://msdn.microsoft.com/en-us/library/bb608626.aspx

No comments:

Elevating LLM Deployment with FastAPI and React: A Step-By-Step Guide

  In a   previous exploration , I delved into creating a Retrieval-Augmented-Generation (RAG) demo, utilising Google’s gemma model, Hugging ...