VSTO3MSI Release Rss Feed

UPDATED RELEASE: VSTO 3.0 MSI deployment code samples (Mar 26, 2008)

Wed, 04 Jun 2008 19:26:17 GMT

The code samples are written in Visual Basic and C#. The following list of projects and samples describes how you can integrate these into your solution to deploy with a Windows Installer file.

Packages - you can add prerequisites to your installer.
1. Office 2003 PIAs.
2. Office 2007 PIAs.
3. VSTO runtime Japanese language pack.

Projects - you can add these custom actions to your setup project.
1. Component Check - check if the Office Primary Interop Assemblies are installed
2. ClickOnceCustomActions - install into the ClickOnce cache
3. DocumentManifestCustomActions - update the document custom properties to point to the assembly
4. InclusionListCustomActions - add an entry to pre-trust your solution

Samples
1. Basic installer - Hello World add-in
2. Additional components - Hello Word add-in plus a helper library (showing deployment with multiple files)
3. Inclusion list - custom action to create an inclusion list entry with the location of the deployment manifest and the public key of the certificate used to sign the manifests
4. Change Manifest - custom action to update the document's custom properties to point to the deployment manifest
5. ClickOnce cache - custom action to install the solution into the ClickOnce cache

UPDATED RELEASE: VSTO 3.0 MSI deployment code samples (Mar 26, 2008)

Wed, 04 Jun 2008 19:18:53 GMT

The code samples are written in Visual Basic and C#. The following list of projects and samples describes how you can integrate these into your solution to deploy with a Windows Installer file.

Projects - you can add these custom actions to your setup project.
1. Component Check - check if the Office Primary Interop Assemblies are installed
2. ClickOnceCustomActions - install into the ClickOnce cache
3. DocumentManifestCustomActions - update the document custom properties to point to the assembly
4. InclusionListCustomActions - add an entry to pre-trust your solution

Samples
1. Basic installer - Hello World add-in
2. Additional components - Hello Word add-in plus a helper library (showing deployment with multiple files)
3. Inclusion list - custom action to create an inclusion list entry with the location of the deployment manifest and the public key of the certificate used to sign the manifests
4. Change Manifest - custom action to update the document's custom properties to point to the deployment manifest
5. ClickOnce cache - custom action to install the solution into the ClickOnce cache

UPDATED RELEASE: VSTO 3.0 MSI deployment code samples (Mar 26, 2008)

Thu, 27 Mar 2008 01:45:07 GMT

The code samples are written in Visual Basic and C#. The following list of projects and samples describes how you can integrate these into your solution to deploy with a Windows Installer file.

Projects - you can add these custom actions to your setup project.
1. Component Check - check if the Office Primary Interop Assemblies are installed
2. ClickOnceCustomActions - install into the ClickOnce cache
3. DocumentManifestCustomActions - update the document custom properties to point to the assembly
4. InclusionListCustomActions - add an entry to pre-trust your solution

Samples
1. Basic installer - Hello World add-in
2. Additional components - Hello Word add-in plus a helper library (showing deployment with multiple files)
3. Inclusion list - custom action to create an inclusion list entry with the location of the deployment manifest and the public key of the certificate used to sign the manifests
4. Change Manifest - custom action to update the document's custom properties to point to the deployment manifest
5. ClickOnce cache - custom action to install the solution into the ClickOnce cache

CREATED RELEASE: VSTO 3.0 MSI deployment code samples (Mar 26, 2008)

Thu, 27 Mar 2008 01:10:54 GMT

The code samples are written in Visual Basic and C#. The folowing list of projects and samples describes how you can integrate these into your solution to deploy with a Windows Installer file.

Projects - you can add these custom actions to your setup project.
1. Component Check
2. ClickOnceCustomActions - install into the ClickOnce cache
3. DocumentManifestCustomActions - update the document custom properties to point to the assembly
4. InclusionListCustomActions - add an entry to pre-trust your solution

Samples
1. Basic installer - Hello World add-in
2. Additional components - #1 + helper library
3. Inclusion list
4. Change Manifest
5. ClickOnce cache