AndyGett
Andy Gettings is the president of Bullseye Consulting which develops and manages customized SharePoint applications and other software and databases for businesses. More
Microsoft Certified Technology Specialist

Microsoft Office SharePoint Server 2007 Configuration


RSS Feed Feed your read!

Archives

July 2008 (12)
August 2008 (1)
September 2008 (1)
October 2008 (2)
January 2009 (2)
April 2009 (1)

Links

Archive
Archive (Calendar)
@AndyGett Twitter
AndyGett LinkedIn
Bullseye Consulting

Tag Cloud

Family, M4300, Recreation, SharePoint, Technology, Virtualization,

Web.config Changes for Debugging ASPX Page’s Codebehind in SharePoint 

Tags:

Instead of getting the "user-friendly", but frustrating-to-a-developer message "An error has occurred", use these two steps to receive the actual error when developing in SharePoint. Works for both MOSS and WSS.

  1. Show the call stack
    Change
    <SafeMode MaxControls="200" CallStack="false" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="false">
    to
    <SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="false">
  2. Set custom errors to False
    Change

    <customErrors mode="On" />
    to
    <customErrors mode="Off" />

 
Posted by AndyGett on 4-Jan-09
0 Comments  |  Trackback Url  |  Link to this post | Bookmark this post with:        
 

Links to this post

Comments

Name:
URL:
Email:
Comments: