Third-party VSTO 2005 SE plug-in for Outlook 2007: what should I signwith a publisher certificate?

Status
Not open for further replies.
O

Ojas

First, I am not using any ClickOnce technology that I am aware of ;)

For a third-party VSTO 2005 SE plug-in for Outlook, what should I sign

with a publisher's certificate versus an internally generated test

certificate? Which of the following do I sign with the publisher

certificate?

1) the plugin application manifest generated by VS 2008

2) the plug-in's installer .msi file that I've created with an

InstallShield like product

3) the plug-in's installer setup.exe file that I've created with an

InstallShield like product

4) plug-in's main assembly .dll file

5) anything else?
 
K

Ken Slovak - [MVP - Outlook]

Re: Third-party VSTO 2005 SE plug-in for Outlook 2007: what should I sign with a publisher certificate?

1: No, manifest files can't be signed.

2, 3, 4: Yes.

5: any dependent assemblies or libraries you've created that will be loaded

by your main assembly.

"Ojas" <ojasrege@yahoo.com> wrote in message

news:d0597896-ec02-4946-9da2-3e860dff6602@d36g2000prb.googlegroups.com...
> First, I am not using any ClickOnce technology that I am aware of ;)

> For a third-party VSTO 2005 SE plug-in for Outlook, what should I sign
> with a publisher's certificate versus an internally generated test
> certificate? Which of the following do I sign with the publisher
> certificate?

> 1) the plugin application manifest generated by VS 2008
> 2) the plug-in's installer .msi file that I've created with an
> InstallShield like product
> 3) the plug-in's installer setup.exe file that I've created with an
> InstallShield like product
> 4) plug-in's main assembly .dll file
> 5) anything else?
 
O

Ojas

Re: Third-party VSTO 2005 SE plug-in for Outlook 2007: what should Isign with a publisher certificate?

On Jul 21, 6:39 am, "
<kenslo...@mvps.org> wrote:
> 1: No, manifest files can't be signed.


For a VSTO 2005 SE plug-in for Outlook 2007, is there anyway to set

the "Publisher:" value when from Outlook 2007 the user does

Tools => Trust Center => Add-Ins

and then clicks on my add-in name?

Right now that field is still <None> even though my add-in is signed.
 
K

Ken Slovak - [MVP - Outlook]

Re: Third-party VSTO 2005 SE plug-in for Outlook 2007: what should I sign with a publisher certificate?

Is the addin signed with a real code signing certificate that traces back to

a certificate authority that's recognized on that computer, or is it

self-generated certificate?

The certificate may need to be installed in the certificates cache, or be

added as a trusted publisher.

"Ojas" <ojasrege@yahoo.com> wrote in message

news:a83bfe51-e955-4ebf-b1da-acb05c1fd4a0@i8g2000pro.googlegroups.com...

On Jul 21, 6:39 am, "
<kenslo...@mvps.org> wrote:
> 1: No, manifest files can't be signed.


For a VSTO 2005 SE plug-in for Outlook 2007, is there anyway to set

the "Publisher:" value when from Outlook 2007 the user does

Tools => Trust Center => Add-Ins

and then clicks on my add-in name?

Right now that field is still <None> even though my add-in is signed.
 
Status
Not open for further replies.
Top