ADO.NET forces unload ODBC Driver

G

Guest

Come across a problem with VB.net application using an ODBC Driver.
On application shutdown, it forces unloading the ODBC Driver without giving
enough time for the driver to handle DLL_PROCESS_DETACH (or
CWinApp::ExitInstance)

We have our own ODBC Driver and found a problem with lengthy driver
unloading process. The ODBC Driver takes more than 3-5 seconds to clean up
during DLL unloading. And it looks like ADO.NET/.NET interrupts normal
unloading process, if it takes more than 2 seconds (or about). We tried to
emulate lengthy unloading process with normal DLL (not ODBC driver) and
DllImport directive in C#, but it seems to work fine.

We tried to use others (SQLite) ODBC driver source code and we get the same
behaviour from Ado.net

Thanks!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top