Quote Originally Posted by Grant Swinger View Post
This link is a good proof of the advantages of .NET, which is that things that are easy to do in VB6 require very complex steps in .NET.
It also proves the advantage of OOP, that is, the operation that can be achieved in one step, which needs to be turned 9 turns in OOP.


https://stackoverflow.com/questions/...com-exe-in-net
Enterprise services will allow you to do just that. You can run a COM component as:

A DLLHost process
A service
An inproc library (this is in the same process as your other code)
There are numerous examples on the internet about these. What it comes down to is:

Decorate your classes that you need to expose to COM with Interfaces
Components that you want to host need to be derrived from ServicedComponent
Decorate your interfaces with a GuidAttribute (use a unique Guid)
Decorate the interfaces and classes that are exposed to COM with a ComVisible(true) attribute
Hope this helps.