How to attach to a process middle tier for debugging

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I'm consulting on a project that has two solutions, a client solution, and a
middletier solution. The middle tier solution is hosted in asp.net.

I want to debug something in the middle tier, and I've been told that I have
to attach to the asp.net process.

So I add a breakpoint on the code in the middle tier. I build the middle
tier solution and then the client solution in debug mode. Then I start the
client application. Then I'm supposed to attach to the ASP.NET process.

I've tried to attach to the asp.net process from both solutions but the
debugger doesnt stop at the breakpoint.

The middletier is not in the client solution, but is referenced

Can Anyone help?
 
MrNetDeveloper wrote:
....
So I add a breakpoint on the code in the middle tier. I build the middle
tier solution and then the client solution in debug mode. Then I start the
client application. Then I'm supposed to attach to the ASP.NET process.

I've tried to attach to the asp.net process from both solutions but the
debugger doesnt stop at the breakpoint.

The middletier is not in the client solution, but is referenced

Can Anyone help?
Click to expand...

Try to start middle tier project in debug mode (I assume, this is
web service or web application). It will launch IE and start the project.
Now you have the actual process and should be able to hit a break point
from you client project.
 
The easiest is probably to;

1. Compile your client to trigger the target function you wish to debug in
the middle tier.
2. Open your middle-tier target project and set break point.(Important:
Ensure there's no other image of this middle-tier anywhere (i.e. GAC, if
applicable))
3.Attach to ASP.NET.
4. Execute your client from windows or console and trigger (from step 1) the
event to start the call.

That should work.
Good luck.
Jeff <www.ruamkwamkid.com>
 
Back
Top