I'm migrating our app from VB6 to .Net using C#
One of our custom dlls is a SQL server connection manager that uses
callbacks to ensure there are no hanging open connections.
The .Net version works fine as long as you call it in .Net but using it with
a VB6 client is another matter. VB6 can see and use all public classes and
methods, where it trips up is when a VB6 object is passed to the dll(.Net),
the dll only sees the passed object as a generic _comObject not as an
instance of the class that it belongs to.
Any ideas?
One of our custom dlls is a SQL server connection manager that uses
callbacks to ensure there are no hanging open connections.
The .Net version works fine as long as you call it in .Net but using it with
a VB6 client is another matter. VB6 can see and use all public classes and
methods, where it trips up is when a VB6 object is passed to the dll(.Net),
the dll only sees the passed object as a generic _comObject not as an
instance of the class that it belongs to.
Any ideas?