Two COM questions

[Uty]

As the subject suggests, I have two questions about using COM objects in C#. I'm using two different objects, each of which is giving me a problem.

The first object ... we'll call it AppXControl. Here's some Visual Basic 6 code I've written which gets the code connected to the COM object.


Private WithEvents xControl As AppXControl.Control
Private xConnector As New AppXControl.Connector

** This line of code is in FormMain_Load()
Set xControl = xConnector.xMonitor

Basically, you instantiate two classes defined in the COM object. The first is a controller -- this is the actual object that catches triggered events and so on. The second is a connector. You instantiate it, and use xConnector.xMonitor to get an xControl object for use in doing COM with ApplicationX.

Here's the corresponding C# code:

public class Form1 : System.Windows.Forms.Form
{
private AppXControl.ControlClass xControl;
private AppXControl.ConnectorClass xConnector = new AppXControl.ConnectorClass();

...

public Form1()
{
InitializeComponent();
xControl = xConnector.xMonitor;
}

...
}


Here's the problem. In the Form1 Constructor, xConnector.xMonitor is returning an object of type AppXControl ... but what I really need here is an object of type AppXControlClass. The COM object itself has no knowledge of this AppXControlClass, it is created by C# when the object is ported to the .NET framework with tlbimp. Is there any way I can get the AppXControl object instead of AppXControlClass without asking the COM object's vendor to rewrite their code? (Which I doubt they'd do anyway.)


Now on to question 2. Basically, I have another COM object that I'm trying to work with, but when I run my application, I get an exception to the effect of "COM object with CLSID {X} not found" ... all the info that needs to be in the registry about that object is there, because my Visual Basic 6 code written for that same object works just fine. Here's what I do:

1. Get .NET interface to COM object with tlbimp.
2. Add COM reference to project.
3. Write some cool code.
4. Compile.
5. Put executable and .NET COM object wrapper on test machine.
6. Run regasm.
7. Run code.
8. Get exception, bang head against wall.

I think it's odd that this procedure works just fine for one COM object but apparently isn't good enough for another COM object. Am I missing something here?

Thanks!

[Tewl]

1. I can't really help you I have seen that problem before but haven't had any need to work with anything other than the Class that is generated.

2. Have you registered the COM object with regsvr32.exe?

[Uty]

Thanks for the reply.

1. Were you able to catch COM object events with the generated Class?

2. I just tried to run regsvr32.exe on the generated .dll and got this error: "x.dll was loaded, but the DllRegisterServer entry point was not found.\nThis file can not be registered."

[Dangermouse]

2. www.google.com/search?q=was+loaded%2C+but+the+DllRegisterServer+entry+point

[Uty]

The original COM object is a .exe. So I guess that would explain that. Still though -- I did not write the COM objects I'm working with. I can't modify them.

[Tewl]

This is probably a stupid question but are you sure they are com objects.

[Uty]

LOL. Yes. I'm sure. I have made use of them as COM objects in VB6.