Removing COM Item from Add References

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

Howard Kaikow

On a multiboot system, I've got:

1. Office XP installed under an OS installed on drive G.
2. Office 2003 and NS .NET 2003 installed under an OS installed on drive J.

When booted to J, if I try to Add Reference in VB .NET, I see a COM object
for Office 10 Object Library on G and another for the Office 11 Object
Library on J.

How do I get rid of the COM object listed for G?
Not just removed from the project, but removed from the list of COM items.

regsvr32 -u doesn't do the deed.
 
Here's some more info.

On my J drive, I have a Win 2000 system that has Office 2003 installed, and
has never had an earlier version of Office installed. I find that the list
of available COM references in VS .NET 2003 includes references for both the
Office 10 object library and the Office 11 object library.

The reference for Office 10 is to G:\Program Files\Common Files\Microsoft
Shared\Office10, which is in an OS on the G drive in this multiboot system.

However, I also note that the system on the J drive has both J:\Program
Files\Common Files\Microsoft Shared\Office10 and
J:\Program Files\Common Files\Microsoft Shared\Office11, each of which has a
different mso.dll.

Looking at the Registry, I see typelib entries for

Microsoft Office 10.0 Object Library in G:\Program Files\Common
Files\Microsoft Shared\Office10\mso.dll
Microsoft Office 11.0 Object Library in J:\Program Files\Common
Files\Microsoft Shared\Office11\mso.dll

My questions include:

1. How did a reference to a never installed version of an Office object
library get included in the registry?
2. What is the purpose of the, apparently, spurious J:\Program Files\Common
Files\Microsoft Shared\Office10?
 
Here's more info:

1. The WinNT directory on drive J is dated 8/20/2003 10:00, so I guess that
is when I did the clean install of Win 2000 on J.

2. J:\Program Files\Common Files\Microsoft Shared\Office11 is dated
10/24/2003 14:31, which is when I installed Office 2003.

3. J:\Program Files\Common Files\Microsoft Shared\Office10 is dated
8/21/2003 19:14..

4. I installed VS .NET 2003 on K to save space on the J drive. K:\Program
Files\Microsoft Visual Studio .NET 2003 is dated 8/21/2003 19:09, so I
expect that J:\Program Files\Common Files\Microsoft Shared\Office10 was
created during the install of VS .NET 2003. This solves part of the mystery.

However, it does not explain why the COM object reference points to
G:\Program Files\Common Files\Microsoft Shared\Office10 instead of
J:\Program Files\Common Files\Microsoft Shared\Office10.

There is the implication that something searched ALL the drives and
determined that G:\Program Files\Common Files\Microsoft Shared\Office10 was
more up to date than J:\Program Files\Common Files\Microsoft
Shared\Office10. I sure hope not, but that's what it looks like.

I'm wondering what will happen if there is ever an update to VS .NET 2003
that needs to update the files in J:\Program Files\Common Files\Microsoft
Shared\Office10. Will it instead/also update the files in G:\Program
Files\Common Files\Microsoft Shared\Office10? I sure hope not as that might
break the Office XP installation in the OS on G.
 
Back
Top