Outlook 2003 shared add-in (NOT VSTO!) deployment problems build with VS2005

  • Thread starter Ken Slovak - [MVP - Outlook]
  • Start date
S

semedao

Hi All,
I developed ad Outlook 2003 add in without using the VSTO module (since I
want it will be abaleto support older outlook versions).
The add in load correctly in the development machine.
When I try to deploy it on other machines it did not load (the registry
loadbehavior key change from 3 to 2)
I already deploy the PIA , my question is if the deployment requirments are
the same as with VSTO when I develop with VS2005 ?
should I also set the CAS , and all other registry keys like in VSTO ?
Or , if not , give me some points where to start to look for the problem , I
did not find nothing in the NET about this situation.
Did MS force to use VSTO when move to VS2005?
an if the answer is yes , how I will support older/other outlook versions
perior to outlook 2003 , If I want to use the new features of NET framework
2 ?
Thanks a lot
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top