How to debug VB.NET DLL(Class Library) from ASP.NET page
Posted on 2003-02-22
In VB6 DLL's and classical ASP, I used to procedure the following way:
I opened the VB6 DLL project, I executed it and when I made a "CreateObject" from an ASP page; objects were instanciated from the running source code (instead of the compiled DLL), so, I was able to debug all my VB6 DLL called from the my classic ASP page.
Now, with VB.NET and ASP.NET I'm not able to do the same thing. Using namespaces, my compiled VB.NET DLL (Class Library) works perfectly. I supposed it would work the same way as VB6, so I execute the VB.NET project in debug mode and with F5, but every object instanciated and used from ASP.NET is created and handled by the compiled DLL, so, it never goes into the source code I'm trying to debug.
I requested some help and I was required to make a change in my "machine.config" file to enable debugging.
So, i changed this line:
<compilation debug="true" defaultLanguage="vb"...>
"debug" was in "false", so I supposed that this would be the solution and I changed it, but nothing happened :(
As you can imagine this is essential for me, and I have not found the way to do it for some weeks. So, I think it's a hard question and i give 200 points for its answer
Could somebody help me ?
Thanks in advance for your valuable help
PS: I hope to be clear, and sorry about my english, it's not my foreign language.