Geek asks and answers

Deploying an Office 2007 Add-in Using MSI Without a Trusted Publisher Certificate - .NET 3.5

With .NET 3.5, is it possible to deploy the Office add-in in a program file directory that is installed for all users and for users so that they do not receive an untrusted publisher warning?

Deploying a VSTO add-in for all users indicates the following:

If you are developing your solution using Visual Studio 2010 and targeting .NET 4, an alternative to signing with a trusted publisher certificate is to install the add-in in the Program Files folder. This place also needs administrative privileges for recording and will be essentially trusted by VSTO, so there will be no trust invitation, even if the solution is not signed with a Trusted Publisher certificate.

If I understand correctly, installing into a directory of program files with an add-in that targets .NET 4 does not require a signature with a certificate from trusted publishers.

Setting up .NET 4 is not an option at this time. If I add a custom action to my installer that grants FullTrust permission to execute code in my deployment target directory, will I still have to sign my manifest with a trusted publisher certificate?

+3
source share
1 answer

If using .NET 4 is not an option, then I think creating an inclusion list should be what you need. You can take a look at these articles:

How to add or remove inclusion list entries
Trusted office solutions using inclusion lists

+1
source

More articles:


All Articles