 Page [ 1 ]
|
|||
| Outlook and .NET Printer Friendly Version | |||
|
Writing code with C# and VB.NET to create Outlook add-ins and other projects | ||
| Topic | |||
|
Path to Addin not showing
Ok I'm working on my first VSTO project. I have created the first pass and have alpha code working in the development environment. Started testing deployment to both a xp64 and Vista 64 stations. Install works and security policy is changed to Fully Trusted with the SetSecurity project. When I start Outlook the addin is not started. I went to the trust center and found my addin in the inactive addin section. Add my addin and checked the entry. The odd thing is the addin name is correct but the path to the dll is empty ! I have checked the registry entries in HKLM and HKCU and the GUID entries in HKCR. All are fine. When I return to the Trust Center My addin is unchecked and in the inactive list. I can only assume it is because there is no path to the dll file. Any Ideas ? The project and install works on the development computer so the problem is with the install. Thanks, MFZ Michael Zwijacz 04-Nov-2009 13:28 |
||
|
|
Eugene Astafiev
04-Nov-2009 16:26
Hello Michael, 1. What version of VSTO do you use? 2. What is the host application for the add-in? 3. What version of Office do you use? 4. Does it work on XP? |
||
|
|
Michael Zwijacz
04-Nov-2009 18:29
Thanks for the response. 1. VSTO 2005 SE 2. Outlook Developing on 2003 Deploying on 2007. Could this be part of the problem ? 3. Developing 2003 Deploying 2007 4. This is working in a VM Server 2003. This is the developing envirionment. MFZ |
||
|
|
Eugene Astafiev
05-Nov-2009 15:07
Michael, >> Started testing deployment to both a xp64 and Vista 64 stations. Does it work on XP one? |
||
|
|
Michael Zwijacz
05-Nov-2009 16:33
No, The Xp 64 has the same problem. |
||
|
|
Michael Zwijacz
09-Nov-2009 09:59
I was wondering if the problem could be that I'm developing on 2003 version of Outlook. The deployment is on 2007 Outlook. When I have developed com solution this was not a problem. Newer versions of an application always supported the older verion of the object model. Is this still true in VSTO ? In regard to the question about XP, There is no XP 32bit. I am developing in a virtual machine with server 2003. This is as close to XP as I can get. The users are on Vista 64 and XP 64. I know bleading edge. But this is what I have to work with. I realy need to solve this problem. Please Help. Thanks, MFZ |
||
|
|
Michael Zwijacz
09-Nov-2009 19:09
Could the problem be that I have created the setup with the project in Debug mode ? Please help Michael Z. |
||
|
|
Michael Zwijacz
10-Nov-2009 22:31
Well I was able to track down the problem. I had to install the full version of Office 2007 in my Virtual Machine development environment. Then I created a new VSTO solution for Office 2007. At that point I copied the classes over to the new project and corrected some minor differences between Office 2003 and 2007 object model. The setup or install on a clean client is a real bear. Confirming that the client has the prereqs is not easy. and I have not been able to figure out how to include the 2007 pia in the install. So for now I'm requiring the install of the pia prior to the install of the project. Making the install process seamless for the users is going to take some work. However I feel I'm in the home stretch. MFZ |
||
|
Page [ 1 ]
|
|||
| Post a new message to this topic. name email  |