can you explain w3wp ,,attaching to w3wp while debugging asp.net internal layers is good
A:
Erm, what? :-) w3wp is just the worker process for an application pool in IIS. Every app pool has one or more worker processes so a failure in a single application pool doesn't kill the whole server (assuming you've used different app pools for each app :-))
What else is there to know? :-)
Steven Robbins
2009-03-24 06:37:36
my project has 4 layers DAL,,BO,,ServiceWrapper,,UI solutionsi need to debug from UI to Dal how to do for this..Now i am finding methods calling ,,for eg in UI client = new ContentAdministrationServiceClient(); client.SetFaq(ref faq); here i will put break point inSetFaq
peter
2009-03-24 06:43:30
in ContentAdministrationServiceClient of servisewrapper and attach that to w3wp,,is there any other way
peter
2009-03-24 06:44:12
If it's ASP.Net then you should connect to the aspnet_wp process.
Steven Robbins
2009-03-24 06:44:45
aspnet_wp is only for IIS 5 IIRC. W3WP is the right process to attach to in IIS 6 and newer.
Jonathan
2009-03-24 12:03:02
A:
W3wp.exe is the "World Wide Web Worker process". I don't see any reason or benefit to attach to it because it will not enable you to debug your ASP.NET application.
If you intend to debug ASP.NET applications, you should be attaching to the aspnet_wp.exe process (which is what Visual Studio does when you press Debug).
Cerebrus
2009-03-24 06:42:50
+1
A:
To attach a debugger set a break point in code that you know will be run (make sure that Debug="True" so that debug symbols are created) and in Visual Studio go Debug -> Attach to Process -> find your site's app pool's w3wp process. If you have several application pools active then w3wp will be listed more than once.
To step into your DAL you will need that compiled with debug symbols as well.
eddiegroves
2009-03-24 08:25:35