[VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Hello all,
I 've develop and deployed an Outlook 2003 Addin using VSTO 2005.
The project runs succesfully on Windows 2000 and Windows XP
I setup the project with no errors on a Windows 2003 Server which runs as a Terminal Server, but the AddIn does not loaded when Outlook starts.
Also there is no Addin in COM AddIn s dialog.
Any ideas?
Many Thanks..
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Isnt there an installer with 05? If you have a setup package created you need to install it from the Add/Remove control panel applette as this sends Terminal Server into "Install Mode". This will give it an absolute filepath as I bet the user home directory path is the one being referenced and its not matching locations, thus not loading.
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Well I did what you said but no difference, the Add In is not loaded :(
I Also follow this example http://forums.microsoft.com/MSDN/Sho...27761&SiteID=1
But i still cannnot see my Addin loaded.
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Rob these examples are refer to solutions developed with VS2003, but my solution is developed with VS2005 + VSTO2005.
Nothing happens. :(
Thanks for your help.
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
So its was not an upgrade from 2003 ok.
Do you have Administrator prividgles on the TS?
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
yes i am the administrator,
I also give FullTrust to application's folder through Caspol.exe.
Re: [VSTO 2005] Outlook 2003 Addin does not loaded on Windows 2003 Terminal Server
Capsol.exe is for scripting security policy changes mainly and even still is not as highly recommended utility over Mscorcfg.msc
Are you running in an Exchange environment? If so perhaps looking at the Exchange Admin panel and giving your Add-In full trust that way, which is the main method.