SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am studing this topic and I would like somebody to point me in the right direction for studying this.

Debug Web Parts
This objective may include but is not limited to: ULS log, and event log, debug.log tracing, developer dashboard

share|improve this question
up vote 4 down vote accepted

This sounds like you're studying for TS: SharePoint 2010 Application Development 70-573.

The part that says what's included are actually practices any development in SharePoint, not specific to Web Parts.

It seems strange to me though, that their list doesn't include the most powerful debugging utility available to a developer - Attaching to w3wp and stepping through your code. It seems they're more interested in having candidates know where log files are kept, rather than actual debugging methods.

Anyway, Andrew Connell did a good blog post on this a while ago for 2007:

For Developer Dashboard, there's plenty about on the web, but first you need to enable it:

Then analyse the output from the Dashboard, here's some info about that:

share|improve this answer
thank you, very useful – Luis Valencia Aug 20 '10 at 22:06

You can check the various tools and techniques here to debug any SharePoint 2010 solution :

share|improve this answer

I think you can just attach the w3wp.exe process to your visual studio debugger and all done.

You should be able to hit the debug point in your code.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.