Debug Class library

I have a c# class library that I am calling from Classic ASP.

Is it开发者_StackOverflow possible to debug this using visual studio? Break points in the class don't work, which isn't surprising.

I am running this on iis7 in the browser, rather than through Visual Studio 2010 because of the fact that I'm using a classic ASP page. Do I need to get this running in Visual Studio in order for this to work?

I also tried to use Response.writes, but they result in: The name 'Response' does not exist in the current context

You need to attach the debugger to the process (either IIS or another debugger that you are using to debug your classic ASP application) that is loading the assembly.

Under VS2010 go to Tools -> Attach to Process (probably the same under 2008 as well).

try to add in the code of the lib: System.Diagnostics.Debugger.Break(); where you want to break. Also ensure the lib is compiled and deployed with the pdb symbols. When the code will reach the instruction, IIS will throw an exception. The system will ask you to attach a debugger, and you're on the way.

I actually wrote an article regarding this:

http://www.jameswiseman.com/blog/tag/visual-studio-2010/

From the article:

1. Open Visual Studio 2010

   This is easy enough if you have it installed. Might be a bit tricky if you don’t ;-)

2. Open your website in Visual Studio

   Again, easy enough.

3. Fire up your web site. I.e. open your browser and navigate to the website.

4. In Visual Studio, click ‘Debug’ Menu -> ‘Attach to process’

5. You may need to tick the box labelled ‘Show processes from all users’

6. ‘Inetinfo.exe‘ if application protection is low or ”dllhost.exe‘ if application protection is higher. You may get an ‘Attach Security Warning’ popup. If so, continue On. It’s a bit scary at first, but if it’s your own app on your own PC, then you’ll be ok.

   

   If you’re worried about this, follow the advice on MSDN.

7. Add a breakpoint to your code, and navigate to a location where you will hit it.

Troubleshooting - Registering pdm.dll

This worked on the first occasion that I tried it. Subsequent attempts were not so successful, and I found a few things that I had to do.

When trying to attach to ‘Script Code’ I got the following warning in the IDE.

Warning: Cannot debug script code. The correct version of pdm.dll is not registered. Repair your Visual Studio 2010 installation, or run ‘regsvr32.exe “%CommonProgramFiles%\Microsoft Shared\VS7Debug\pdm.dll”‘.

Just follow these instructions.

Troubleshooting - Restart IIS

This also helped on one occasion. Can’t really say why.

You will make your life much easier all round if you wrap you .net classes in a web service then call the web service from the classic asp pages.

For debugging, attach the debugger to the process as described in other answers.

For tracing, I find very handy the combination between System.Diagnostics.Trace.Writeline() in the class library and an OutputDebugString listener like DebugView.