1

I have some legacy Web Services written in C# ASP.NET. There is a specific object in a library used by the Web Service that I need to inspect. Setting a breakpoint in the web service doesn't do anything.

This is made harder by the fact that the code is so horrendous that the entry point to the Web Service callout is not obvious.

Improve this question
0

4 Answers 4

Reset to default
3

Here are some reasons your breakpoint might not be working:

  1. You're attaching the debugger to the wrong process.
  2. The PDB for your assembly does not match the assembly (Modules window shows PDB load status). Perhaps the PDB is old.
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

You might try putting a line in where you want it to stop using System.Diagnostics.Debugger.Break() or System.Diagnostics.Debugger.Launch().

Improve this answer

Comments

0

Are you running the build using debugging? I think ASP.net doesn't run using debugging by default.

Improve this answer

1 Comment

Are you including any compiled dlls?
0

If you're running some website that uses the web service, you can manually attach the debugger to the web service process as well as the website, using Debug - Attach Process...

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.