COM Add-in deployment

[Ashok]

Hi,

I'm creating a COM Add-in to Microsoft Visio using Visual Studio 2008. I
followed the following procedure.

1. Created an Extensibility Shared Add-in Project.
2. In the onConneciton method, added Menu and MenuItem to the Visio
Application.
3. Performed specific action when the Menu Item is clicked.
4. Excluded the Visio.dll and Office.dll from the deployment project.
5. Had the following as the pre-requisites for the installation - .Net 3.5
framework and Visio Insatllation by searching the Registry key of Visio 12.0
registry key.

Now the Add-in msi gets installed in a target PC and the intended
functionality works as expected. On the Tools --> Trust Center --> Add-ins
page, I could see my Add-in listed as COM Add-in. But the Publisher is shown
as None. Should I do anything specific for that.

Also I would like to know if signing this Add-in is mandatory to make it
available to our customers. On searching, I see items like CAS and Trusting
etc., Please let me know if those things are mandatory for an Add-in.

Also, how will I confirm that the Microsoft PIA's or the VSTO Runtime are
not distributed along with my Add-in installer. I do not see the Microsoft
PIA's or the Visual Studio Tools in the setup project pre-requisites
settings. If this is not listed there, does that mean the PIA's are not
needed for this Add-in.

Any help on this will be greatly appreciated.

Thanks,
Ashok.

 

[Nikolay Belyh]

Hi,

I'm creating a COM Add-in to Microsoft Visio using Visual Studio 2008. I
followed the following procedure.

1. Created an Extensibility Shared Add-in Project.
2. In the onConneciton method, added Menu and MenuItem to the Visio
Application.
3. Performed specific action when the Menu Item is clicked.
4. Excluded the Visio.dll and Office.dll from the deployment project.
5. Had the following as the pre-requisites for the installation - .Net 3.5
framework and Visio Insatllation by searching the Registry key of Visio 12.0
registry key.

Now the Add-in msi gets installed in a target PC and the intended
functionality works as expected. On the Tools --> Trust Center --> Add-ins
page, I could see my Add-in listed as COM Add-in. But the Publisher is shown
as None. Should I do anything specific for that.

Also I would like to know if signing this Add-in is mandatory to make it
available to our customers. On searching, I see items like CAS and Trusting
etc., Please let me know if those things are mandatory for an Add-in.

Also, how will I confirm that the Microsoft PIA's or the VSTO Runtime are
not distributed along with my Add-in installer. I do not see the Microsoft
PIA's or the Visual Studio Tools in the setup project pre-requisites
settings. If this is not listed there, does that mean the PIA's are not
needed for this Add-in.

Any help on this will be greatly appreciated.

Thanks,
Ashok.

Hello, Ashok

- Signing is not required, but is recommended.
To sign your add-in you need to order a code signing certificate from
one of the certification authorities, such as Verisign, Thawte, or
Comodo. Normally code signing certificate costs from $500/year to $150/
year. To get a certificate you'll need to provide the authority you
choose with your identity data, such as phone number and your compnay
registration record copies, or (in case you are an individual and not
a company) with your private data, e.g. a passport scans)

- VSTO runtime is NOT required if you create a "Shared add-in". It is
required in case you create a VSTO addin (e.g. if you create addin
using "Visual Sutio Tools for Microsoft Office")

- PIAs are normally installed by Visio itself.

Regards, Nikolay

 

[Ashok]

Hi Nikolay,

Thanks for your response.

Regards,
Ashok.

 

[Ashok]

Hi Nikolay,

Thanks for your response.

So signing is what is required to show the publisher information in the
Trust Cente --> Add-in's page?

Also, I believe a strongname is also not required for my add-in assembly if
signing is not required.

Regards,
Ashok.

 

[Nikolay Belyh]

Hi Ashok,

That's right, digital signature is required to show the publisher's
information in the trust center -> addin's page, and strong name is
not required.

Regards, Nikolay.