Print Page | Close Window

Manual repair of the missing Object Mapper

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=177
Printed Date: 07-Nov-2025 at 12:04pm


Topic: Manual repair of the missing Object Mapper
Posted By: Customer
Subject: Manual repair of the missing Object Mapper
Date Posted: 12-Jul-2007 at 1:40pm

I recently tried to upgrade to v3.5.1.1 by uninstalling the old version and reinstalling the new version. The install seemed to go ok but the Object Mapper Installer comes up with an error

 Command “Tools.InstallCommunityControls” is not valid




Replies:
Posted By: IdeaBlade
Date Posted: 12-Jul-2007 at 1:43pm
Manual Repair of the Missing Object Mapper

The usual cause of a missing Object Mapper is that Visual Studio has a pointer to a “bad” Object Mapper Add-in.

Check for “bad” Add-in

ð    Launch Visual Studio

ð    Select Tools ? Add-in Manager … from the menu.

Add-in Manager probably shows that the IdeaBlade Object Mapper is present as in the following:

If you don’t see the Object Mapper listed, there is some other problem. Please contact Customer Support.

Visual Studio “remembers” the last time it tried to use this Add-in and it can’t load what it remembers.

Copying a new version of the Object Mapper Add-in on top of the old copy won’t work. Visual Studio won’t try to load it again until we make it forget about this Add-in.

The trick is to

·         Rename the IdeaBlade.DevTools.Orm.AddIn file temporarily,

·         convince Visual Studio that it is gone,

·         restore the Add-in file name, and

·         cause Visual Studio to discover it anew.

The AddIns Directory

Visual Studio looks for an XML file in its “AddIns” directory.

That directory varies depending upon your edition of Visual Studio and how you installed it.

The preferred location is:

about:blank../../All%20Users/Application%20Data/Microsoft/MSEnvShared/AddIns - C:\Documents and Settings\All Users\Application Data\Microsoft\MSEnvShared\AddIns

For the All Users location, you must have the Show Hidden Files and Folders option turned on to see the Application Data folder.

Alternatively, the directory may be in the user’s directory space at

%HOMEPATH%\My Documents\Visual Studio 8\AddIns

You can copy and paste this into Windows Explorer. Realize that this directory may not exist.

Jiggle the Object Mapper AddIn file

We can proceed now that we know where Visual Studio keeps its Add-in information.

ð    Exit Visual Studio.

ð    Navigate to the Visual Studio “AddIns” directory

ð    Rename IdeaBlade.DevTools.Orm.AddIn to IdeaBlade.DevTools.Orm.AddInXX

ð    Confirm for Windows that it is OK to change the file extension.

ð    Launch Visual Studio.

ð    Select Tools ? Add-in Manager … from the menu.

ð    Verify that “IdeaBlade Object Mapper” is no longer listed.

If you still see the Object Mapper listed, you won’t be able to revive the Object Mapper. There is some other reference to it somewhere. Please contact Customer Support.

ð    Exit Visual Studio.

ð    Restore IdeaBlade.DevTools.Orm.AddInX back to IdeaBlade.DevTools.Orm.AddIn

That should do it. Now we verify that the Object Mapper is installed.

ð    Launch Visual Studio again.

ð    Look for “IdeaBlade Object Mapper” at the top of the Tools menu.

 

Still can’t make it appear?

You’ve tried the Object Mapper Installer, you’ve jiggled the AddIn file, and it still won’t appear in the Tools menu.

You can see the Object Mapper in the Add-in Manager; it just won’t appear in the Tools menu.

Perhaps you customized your installation of Visual Studio. Excluding VB or C# will cause this behavior.

Try the following:

ð    Open the Visual Studio Tools menu.

ð    Select "Customize…".

ð    Select “AddIns” on the Commands tab.  You should see IdeaBlade Object Mapper in the Commands window.

ð    Select and drag the “IdeaBlade Object Mapper” onto the Tools Menu just above "Connect to Device.

 

 

Before drop

After drop




Print Page | Close Window