![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
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? |
#2
|
|||
|
|||
![]()
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. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007. Reminder Manager, Extended Reminders, Attachment Options. http://www.slovaktech.com/products.htm "Ojas" wrote in message ... 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? |
#3
|
|||
|
|||
![]()
On Jul 21, 6:39*am, "Ken Slovak - [MVP - Outlook]"
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. |
#4
|
|||
|
|||
![]()
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. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007. Reminder Manager, Extended Reminders, Attachment Options. http://www.slovaktech.com/products.htm "Ojas" wrote in message ... On Jul 21, 6:39 am, "Ken Slovak - [MVP - Outlook]" 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. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Outlook VSTO 2005 plug-in installer: CLSID = ? | Ojas | Add-ins for Outlook | 3 | July 21st 09 05:02 AM |
vsto 2005 se/outlook 2003 add-in doesn't load | Rajesh Deshpande | Add-ins for Outlook | 3 | May 3rd 07 10:33 PM |
VSTO 2005 SE add-in for Outlook 2003 & Outlook 2007? | Michael | Add-ins for Outlook | 3 | January 23rd 07 08:16 PM |
VSTO 2005 SE is final, free (w/VS Pro 2005) and supports OL2003 *s | Tadwick | Outlook and VBA | 5 | November 15th 06 06:54 PM |
Outlook 2007 Add-in using VSTO 2005 SE | Kenn | Outlook - Using Forms | 1 | November 4th 06 03:27 AM |