Should I include the manifest file in registry when deploying VSTOAddin?

[vincent.y.chan]

Hi,

I was wondering if someone out there could help me. I'm developing an
addin for outlook 2007 and I have been testing out the deployment to
other computers. My question is do I need to include the location of
the manifest file in the registry location of my addin project (HKCU
\software\Microsoft\Outlook\Addins\MyAddin) ? The reason why I'm
asking is that I have a registry value "manifest" which has the
location of the manifest file (C:\Program Files\My Project
\MyAddin.dll.manifest). If I delete this registry key and I open
outlook 2007, I cannot see any of my buttons on the ribbon, so I'm
guessing the manifest is needed?

Much appreciated,

Vincent

 

[Ken Slovak - [MVP - Outlook]]

Is this a VSTO addin? I usually only see that registry entry for a VSTO
addin, if you look at the manifest file does it reference VSTO at all? If
that's the file you mean it's needed for the VSTO addin to be able to be
loaded.

If this is a VSTO addin then most likely the manifest file is included in
the primary output from your project content in the setup project.
Right-click on that primary output and select Outputs and see if that lists
the manifest file.

 

[vincent.y.chan]

Hi Ken,

Thanks for getting back to me so quickly Ken. You are correct, my
addin is a VSTO addin. I have looked into my manifest file and it
does include a references to my addin project (i.e references to
myAddIn.dll)

I'm unable to find the "outputs" area that you have identified below..
it would be located somehow in my setup project right?

If my manifest file is included in the "outputs" area, does that mean
I wouldn't need the manifest value in the registry? I have had weird
behaviour before where my addin project would work without the
manifest value in the registry but now it seems like I need it again
to work.

thanks,

Vince

Is this a VSTO addin? I usually only see that registry entry for a VSTO
addin, if you look at the manifest file does it reference VSTO at all? If
that's the file you mean it's needed for the VSTO addin to be able to be
loaded.

If this is a VSTO addin then most likely the manifest file is included in
the primary output from your project content in the setup project.
Right-click on that primary output and select Outputs and see if that lists
the manifest file.

--
Ken Slovak
[MVP - Outlook]http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Optionshttp://www.slovaktech.com/products.htm

Hi,

I was wondering if someone out there could help me. I'm developing an
addin for outlook 2007 and I have been testing out the deployment to
other computers. My question is do I need to include the location of
the manifest file in the registry location of my addin project (HKCU
\software\Microsoft\Outlook\Addins\MyAddin) ? The reason why I'm
asking is that I have a registry value "manifest" which has the
location of the manifest file (C:\Program Files\My Project
\MyAddin.dll.manifest). If I delete this registry key and I open
outlook 2007, I cannot see any of my buttons on the ribbon, so I'm
guessing the manifest is needed?

Much appreciated,

Vincent

 

[vincent.y.chan]

Hi Ken,

I just checked my project again, and I noticed that I did not include
the manifest file in the primary output area. Should I include it
there? or do you have to do include it there?

thanks,

Vince

Hi Ken,

Thanks for getting back to me so quickly Ken. You are correct, my
addin is a VSTO addin. I have looked into my manifest file and it
does include a references to my addin project (i.e references to
myAddIn.dll)

I'm unable to find the "outputs" area that you have identified below..
it would be located somehow in my setup project right?

If my manifest file is included in the "outputs" area, does that mean
I wouldn't need the manifest value in the registry? I have had weird
behaviour before where my addin project would work without the
manifest value in the registry but now it seems like I need it again
to work.

thanks,

Vince

Is this a VSTO addin? I usually only see that registry entry for a VSTO
addin, if you look at the manifest file does it reference VSTO at all? If
that's the file you mean it's needed for the VSTO addin to be able to be
loaded.

If this is a VSTO addin then most likely the manifest file is included in
the primary output from your project content in the setup project.
Right-click on that primary output and select Outputs and see if that lists
the manifest file.

--
Ken Slovak
[MVP - Outlook]http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Optionshttp://www.slovaktech.com/products.htm

 

[Ken Slovak - [MVP - Outlook]]

Make sure your project settings are to show all files. You should be able to
see the primary output from the code project and right-click to see the
outputs. Leave the registration of the manifest file alone, it's needed.

 

[Ken Slovak - [MVP - Outlook]]

I've never had to manually play with that at all, it all was done
automatically by the new VSTO addin wizard. What your project currently
looks like I have no idea. Try creating a new VSTO addin project and see
what you get in the way of outputs. I always get that manifest in my
outputs.