The problem is my application leaves the database.dll open on the
server when the application shuts down. I have to go to the server to close the
dll.
How do I close the database.dll? How should I handle the library
dispose() method. Is that the source of my problems? Should I garabge collect in my application?
Steve
Marc,
The application exe only runs on the server (share) so, I can’t see the open dll on my machine. I have to go to the server to see the open dll and close it (major pain). I don’t see the application exe open along with the dll only the dll. Basically, the exe calls the ADO.Net dll and an ADO.Net Library dll. I don’t see the library dll open either and I close the dB. Tomorrow I was thinking of null’ing out the Library object that I call and also calling GC.collection in the closing_event()
The only other thread I have is a thread that tells me if the application is already running or not (getProcesses()). Since only one instance of the application is running (starting) the second thread should never be created ….but I’ll check
Any other ideas? How do I test to see if it’s closed()? The OK and the Cancel button on the form itself already has the close() method. I also can't Release compile to the server because the dll file is open. and I get an error What about something like:
if (this not closed)
this.close();
Steve
