Blog Home  Home RSS 2.0 Atom 1.0 CDF  
CLYDE BARRETTO's BLOG - .NET etc. - Tips for Debugging SharePoint WebPart\WebParts during Code Development
Visual Studio/.NET/Smart Client/SharePoint
 
 Thursday, November 05, 2009

When adding a web part to a Web Page in DESIGN MODE OR implicitly RUNNING a web part when you load a page,you might face issues like the page not loading due to recent code changes in the web part code.

 

Here are some basic steps to troubleshoot and Debug the code in your SharePoint web part.

 

** IMPORTANT NOTE: The steps should ONLY be really used in your DEVELOPMENT ENVIRONMENT. Once you are done with your debugging\troubleshooting – please REVERT your edits. If these changes get into your production site they could cause security\performance issues. To make it simple make a copy of your web.config before you start.

 

Viewing the CALL STACK on your web page – Open your SharePoint Web Site’s web.config

  1. Find the tag <SafeMode MaxControls="200" CallStack="false". Change the CallStack value to true
  2. Find the tag <customErrors, set the mode=”RemoteOnly”
  3. Run your web page

DEBUGGING CODE in your Web Part using Visual Studio 2005\2008

  1. Set the debug flag to true in web.config < compilation batch="false" debug="true">

  2. Open your Web Part Code Solution in Visual Studio
    • Go to Project properties, in the Debug tab make sure your “Start browser with URL” points to your SharePoint site where your web part is hosted
    • Make sure your break points are set. Click F5.
11/5/2009 1:55:32 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0]   .NET 2.0 | Developer Productivity | MOSS 2007 | SharePoint | Visual Studio 2005 | Visual Studio 2008 | WebPart  | 
Name
E-mail
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):

Copyright © 2012 Clyde Barretto. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme: