DevForce Classic: Object Mapper not loading after 3.6.5.1 upgrade

Object Mapper not loading after 3.6.5.1 upgrade

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=1036
Printed Date: 10-Jun-2026 at 5:28pm

Topic: Object Mapper not loading after 3.6.5.1 upgrade

Posted By: Mike U
Subject: Object Mapper not loading after 3.6.5.1 upgrade
Date Posted: 26-Dec-2008 at 8:37am

I recently upgraded from 3.6.0.3 to 3.6.5.1 and not the object mapper does not now appear in the tools menu. It does show up in the addin manager list, but when it is selected it does not load into the tools menu.

I've messed arround with the AddIn paths and shutting down and restarting VS many times. Resharper 4.0 does seem to load successfully, but it seems to use a different mechanism, because I don't see a .AddIn file in its path.

Any suggestions would be welcome.

Replies:

Posted By: davidklitzke
Date Posted: 26-Dec-2008 at 11:13am

Mike,

Do you get an error messsage when you try to load the Object Mapper such as:

Error message: Error not specified

Error number: 80004005

If so, you might want to view post:

http://www.ideablade.com/forum/forum_posts.asp?TID=1031&PID=3737#3737 - http://www.ideablade.com/forum/forum_posts.asp?TID=1031&PID=3737#3737

It appears that this poster achieved success by changing the AddIn path and moving some files around.

Are you using XP or Vista?

Are you using a non-English OS and/or non-English Visual Studio?

Posted By: Mike U
Date Posted: 29-Dec-2008 at 8:14am

David,

I did read that thread before posting. His issue was getting an error when selecting in AddIn manager. My issue is I don't get an error, it just never loads in the Tools menu.

Nevertheless I did try the solution he proposed, but it was not successful. Any other suggestions?

Posted By: davidklitzke
Date Posted: 29-Dec-2008 at 2:44pm

Mike,

If you see the Object Mapper in the addin manager list, that's usually a sure sign that Visual Studio thinks that you have a "bad" addin and doesn't even try to load your addin. Try the "rename" trick described in the Troubleshooting section of the installation guide. If that doesn't work, try uninstalling ans reinstalling Visual Studio. It's a lot of work, but I have had good experiencewith this in the past.

Posted By: Mike U
Date Posted: 30-Dec-2008 at 7:57am

David, thanks that worked.