Moving C# add-in project from one machine to another

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bob Steagall - 21 Apr 2005 21:53 GMT

I have an add-in I've written in C# with VS.NET2003 on my office
workstation, and I'm finally happy with it. How do I move the
add-in project to another machine (my laptop) so that it will
still compile and run?

I've copied the project files to my laptop, re-built the add-in
and the add-in installer on the laptop. I've run the installer
on the laptop and add-in and the other files are being placed in
the correct directory. However, I cannot start up the add-in
from the Add-in Manager dialog. When I do, I get an 80040154
error with the usual helpful message "Class not registered".

What am I doing wrong here?

TIA for your help.
----------------

--Bob

Bob Steagall
Medical Numerics, Inc.

Reply to this Message

"Ed Dore [MSFT]" - 21 Apr 2005 23:42 GMT

Hi Bob,

The fact that it's appearing in the Add-in Manager dialog indicates that
you've got it registered properly under the VS registry hive. But I suspect
that the setup might not have registered the assembly for COM Interop.
Meaning that COM cannot create your component via it's ProgID.

Double check your installation project and verify that the "Register"
property is set to "vsdrpCOM". If this is missing, the proper registry keys
are not added to register the CLSID and ProgID of your IDTExtensibility2
derived object.

If you are building the project on the other machine, ensure that the
"Register for COM Interop" property is set to True, in the project's
Properties Page (under the "Configuration Properties\Build" folder).

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.

Reply to this Message

Bob Steagall - 22 Apr 2005 02:13 GMT

Ed,

Thanks for your help. Turned out to be even simpler. Somehow (I don't
understand how this happened, probably something stupid on my part) a
mismatch developed between the ProgID and the add-in name in the registry
(under HKLM\Software\Microsoft\VisualStudio\7.1\addins). The ProgID was
"MNDevTools" and the registered add-in name was "MNDevTools.connect".
No wonder VS couldn't find it!

>Hi Bob,
>
[quoted text clipped - 16 lines]
>
>This post is 'AS IS' with no warranties, and confers no rights.

----------------

--Bob

Bob Steagall
Medical Numerics, Inc.

Reply to this Message

"Ed Dore [MSFT]" - 22 Apr 2005 17:33 GMT

That was probably fun to track down :-)

I'll add this to my list of gotcha's with that "Class not registered" error.

Thanks for following up and letting us know what the resolution was.

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.

Reply to this Message

Moving C# add-in project from one machine to another

Free Magazines