Re: Outlook 2003 shared add-in (NOT VSTO!) deployment problems build with VS2005 "Ken Slovak - [MVP - Outlook]" <kenslovak[ at ]mvps.org> 02.08.2006 13:35:09 Please do not multi-post. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003 Reminder Manager, Extended Reminders, Attachment Options http://www.slovaktech.com/products.htm "semedao" <semedao[ at ]community.nospam> wrote in message news:ury2pejtGHA.324[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > 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 >

Outlook 2003 shared add-in (NOT VSTO!) deployment problems build with VS2005 "semedao" <semedao[ at ]community.nospam> 02.08.2006 14:29:20 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