I didn't solve the problem of the w3wp.exe process being killed by visual studio but here is the workaround I am using.
1) Start the debugger. It will then kill the w3wp.exe process and error with "w3wp.exe process not running" (Which is a great error message considering it is what killed the process in the first place)
2) Open web browser and go to SharePoint site... this should start the w3wp.exe process
3) In Visual Studio, go to tools->attach to process. You should then be able to naviage to the w3wp.exe process and click attach.
That's it your ready to go.
You can tell if the debugger is working by hitting refresh in your browser. You should see the words "Ready" flicker in the bottom right hand corner of visual studio
Main Topics
Browse All Topics





by: shailaja_kumarPosted on 2009-03-10 at 02:01:47ID: 23844501
One of the reasons could be the App pool identity problem, check under which account the process is running and assign the user to the PowerUser group.