• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Destroying legavy COM objects in VB.NET

V

VTSteevo

n00b
Joined
Jun 2, 2004
Messages
24
I have searched Google many times for this problem, can't find a solution.

I am using a legacy COM Libraby written in VB6. The three objects that I use are:
DBConnect, Document, Application. At the end of my program I write DBConnect.Logout(), however it won't let me do that if Document or Application objects are still present.

In VB6 I just wrote Document = Nothing; Application = Nothing. In .NET this does not have the same effect. I read on MSDN that in .NET the object does not get destroyed when you set it to nothing, but it gets destroyed when the garbadge collector goes through it. Since this library is an SDK kit, i can't see the code, nor can I edit/add anything to it. Might you have any idea on how to force-destroy an object in VB.NET ?

Steve
 
You must log in or register to reply here.
Back
Top