J
James Radke
Hello,
I am using VB.NET to call an unmanaged DLL which contains some functions.
When I call the DLL from a windows application, it all works fine. When I
place the same code in a webform application, my call to the first
initialization routine simply hangs (i.e. in debugger it shows the code
starts executing, but control never comes back to the debugger).
This DLL uses the MFC42.DLL and MSVCRT.DLL which is in the WINNT/SYSTEM32
folder as well as two other DLLS in the DLL application folder. The system
I am trying to run this on is a Windows 2003 server.
I have both the WINNT\SYSTEM32 and the DLL Application folder in the path
statement.
Can someone explain to me why the call is working from a windows vb.net
application and not from an webform vb.net application? Or, can someone
point out what I should look into to try and correct this issue?
Thanks!
Jim
I am using VB.NET to call an unmanaged DLL which contains some functions.
When I call the DLL from a windows application, it all works fine. When I
place the same code in a webform application, my call to the first
initialization routine simply hangs (i.e. in debugger it shows the code
starts executing, but control never comes back to the debugger).
This DLL uses the MFC42.DLL and MSVCRT.DLL which is in the WINNT/SYSTEM32
folder as well as two other DLLS in the DLL application folder. The system
I am trying to run this on is a Windows 2003 server.
I have both the WINNT\SYSTEM32 and the DLL Application folder in the path
statement.
Can someone explain to me why the call is working from a windows vb.net
application and not from an webform vb.net application? Or, can someone
point out what I should look into to try and correct this issue?
Thanks!
Jim