Hi

OK. It seems one is prevented from automatically 'registering for COM
interop' in the Configuration Properties if it's an .EXE project.
Tlbexp works and creates a .tlb but examining it with OLE viewer, the
publicly exposed .NET classes map to IDispatch interfaces with no
properties or methods. That doesn't seem right.

The current way we're getting round this is by using a wrapped .NET
dll which the COM components talk to. Then we use remoting from the
.NET dll to the .NET executable to communicate. But this seems crazy -
having to open a port for two .NET components to talk to each other?!

So, I did remember a posting related to generating CCW for .NET
executables but I can't seem to find it anymore. Also, what's the
standard way to solve this seemingly standard problem?

Cheers

Emma Middlebrook
emma_middlebrook@fastmail.fm