Welcome! and rules
Joel on Software
How to debug a complex solution
I am busy developing a distributed application. I decided to make the client a windows forms application (C#) that talks to a webservice (responsible for the database stuff). I also have a layer of logic between the webservice and the client (for making the proxied objects smart, ie. wrapping them up).
Assuming you've got your webservice compiled as a debug DLL, and your web.config is set for debug, just attach VS to the aspnet_wp.exe executable, and attach to the webservice. Set a breakpoint in your code, and you should be good to go.
Thanx. So far, though, I have all the projects in one solution. If I attach VS to the WebService, it blocks - no way to start the Client. I guess, I will just have to make two solutions... Pity though, but it sort of relates to debuging ActiveX-EXEs in VB6.0.
Duh... OK, now it seems to make sense: A debugger can only attach to one process at a time. The WebService must run in a seperate process, ergo can't be debugged with the same debugger instance as the rest of the application.
Great, Mark! I will try that first thing tomorrow morning!
If you add the "Network Service" or ASPNet user account to the "Debugger Users" group, VS.Net will auto-attach to the web server and allow you to step inside of the Web Method from the Web Client.
Fog Creek Home