I have a package of COM objects written in C++ in version 6. It is
installed separately and shared by several applications. Then I have
a .NET application written in VS2005 that uses these objects. It is
installed by a .NET setup project. I excluded all the COM dll's so
that they don't get unregistered when the .NET app is uninstalled.
After uninstalling the .NET app I can still create objects but I
cannot assign an object to a "WithEvents" variable in VB6 if that
object is crossing a process boundary. In-process it works fine but
out-of-process it flings me an "automation error". All my COM events
are automation-compatible, discoverable with
IConnectionPointContainer, etc., and have not given me any trouble in
7 or 8 years of use until now.
Any clue what .NET is clobbering and how I can fix it? I've gone over
the setup project looking for anything funny, including the registry
keys, and whatever it is I'm missing it.
Thanks, Carl