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
Subscribe to:
Post Comments (Atom)
Disable Microsoft Defender for Cloud for Visual Studio Subscription (MSDN)
I use a visual studio pro subscription which comes with $150 azure cloud credit, for some reason Microsoft Defender for Cloud was turned on ...
-
Error 15401: Windows NT user or group '%s' not found. Check the name again. SELECT name FROM syslogins WHERE sid = SUSER_SID ('Y...
-
Finally, it is time. E4SE 811 and eBackoffice 736 will replace our current 810b/735a environment after staying so many years. Just got the n...
-
/etc/ipsec.config conn ios keyexchange=ikev1 authby=xauthrsasig xauth=server lef...
No comments:
Post a Comment