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 :(

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.

Daniel,
What you described work in VB6, as VB6 changed registry entries so that ASP
found the DLL within VB6 when it did the CreateObject.

VB.NET does not rely on the registry when being called from ASP.NET.

All you should have to do, is open your ASP.NET project, put break points in
your VB.NET dll, run your ASP.NET project (from the IDE).

NOTE: This works better when both projects are within the same solution.

Hope this helps
Jay