Outlook: Removing a menu installed by a VB .NET add-in

  • Thread starter Thread starter Howard Kaikow
  • Start date Start date
H

Howard Kaikow

I am using Office 2003 and VB .NET 2003.

MSFT KB article 302896 includes a step by step example demonstrating how to
build a COM add-in using VB .NET.
The example works with Access, Excel, Outlook, Powerpoint and Word.

For Outlook, the add-in works as advertised.
However, using the add-in's uninstall project does not remove a menu item
that was added by the add-in.
Note that VB .NET add-ins cannot be listed in the Office COM Add-ins menu.

I've not (yet) noticed any bug in the KB article's example.
If there are no such bugs, then might there be a bug in VB .NET add-ins
working with Outlook?
 
Suddenly, the problem has corrected itself, at least temporarily, but the
problem is now back.
I made no code changes.
The menu item was deleted the last time I uninstalled the COM add-in.
As we speak, I will do the following:

1. Install the COM add-in.
2. Run Outlook.
3. Uninstall the COM Add-in.
4. Run Outlook. Menu item was not removed.
 
Hi Howard,

Let's me, myself and I continue this discussion.

I spoke to OUR partner, WE.
WE seems to believe that HE found the cause of the problem.

After using the uninstall project in the add-in's solution, WE located an
orphan key in the registry at:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\AddIns\VBNETMyCOMAddin.C
onnect]

WE deleted the key and since then, none of US has encountered the problem
described in YOUR posting in this thread.

It appears to US that a registry key got corrupted for Excel.
Deleting that key seems to have also fixed the problem for Outlook.
Howard, hope this was of some help.
--
http://www.standards.com/; See Howard Kaikow's web site.
Howard Kaikow said:
Suddenly, the problem has corrected itself, at least temporarily, but the
problem is now back.
I made no code changes.
The menu item was deleted the last time I uninstalled the COM add-in.
As we speak, I will do the following:

1. Install the COM add-in.
2. Run Outlook.
3. Uninstall the COM Add-in.
4. Run Outlook. Menu item was not removed.
Click to expand...
 
In general, you should create the menu command as temporary, so that there
is no need to remove it if the add-in is uninstalled.
 
Yes, but I'm just running the KB example.

--
http://www.standards.com/; See Howard Kaikow's web site.
Sue Mosher said:
In general, you should create the menu command as temporary, so that there
is no need to remove it if the add-in is uninstalled.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
Click to expand...
 
The KB example isn't that good for Outlook. The Items Command Bar sample
from http://www.microeye.com is much better.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Howard Kaikow said:
Yes, but I'm just running the KB example.
Click to expand...
 
All too many examples in the KB and books are not well thought out or
tested.
For example, I just encountered an example for automating Word from VB .NET
that set DisplayAlerts to wdAlertsNone, but did not reset to wdAlertsAll. No
excuse for that.

I'll take a look at the microeye example.
Thanx.
 
I downloaded that example some time ago.
It is in VB 6.
Converting to VB .NET is made difficult since VB .NET will not import
designers.
As we speak, I'm important the VB 6 .vbp to VB .NET 2003.
Pause ...
 
.... I'm back.

As expected, the upgrade of the VB 6 project to VB .NET failed because VB
..NET cannot upgrade designers.
In addition, there were 27 warnings that likely can be ignored.

A VB.NET version of the example would need to be developed from scratch.
 
I was pointing you to that sample, just to see the way that CommandBars are
handled. MSDN has a VB.Net sample of an Outlook COM add-in. There's a link
on my page at http://www.outlookcode.com/d/index.htm#dotnet

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Back
Top