Developer Tip: Debugging your SharePoint 2010 Solution

by Oscar 6. April 2010 01:40

Problem
If you run into a scenario where you have modified the web.config file on the root IIS Site to output the stack trace and and in addition you have switched your customErrors=off but still cannot see the stack trace, what do you do?

Solution
You can temporarily modify the web.config file located under the virtual directory _layouts, restart IIS and you should see the error details at that point.

Hope this helps,

-Oscar

Tags:

Comments

4/6/2010 2:15:01 AM #

Pingback from topsy.com

Twitter Trackbacks for
        
        Oscar Medina | Developer Tip: Debugging your SharePoint 2010 Solution
        [sharepointace.com]
        on Topsy.com

topsy.com | Reply

5/20/2010 9:20:24 PM #

Pingback from 139.cmanager.org

330i Halo Projector Headlight Bulb, 330i Horsepower Fifth Generation Sequential Manual Gearbox

139.cmanager.org | Reply

Add comment




  Country flag

biuquote
  • Comment
  • Preview
Loading



Powered by BlogEngine.NET 1.5.0.7
Theme by Mads Kristensen

About Oscar

Oscar Medina - SharePoint Solutions Architect

I am a SharePoint Solutions Architect and Managing Partner at SharePointAce Consulting Group, LLC.  I have over 13 years of software development experience. 

Previously a Consultant at Microsoft Consulting Services (MCS) North West Region with focus on the SharePoint Products and Technologies Platform.  I have been involved with SharePoint since it's first version (SharePoint 2001) and have grown more gray hair providing solutions ever since :)

Author of the CQWP – Recurring Calendar Events at http://cqwprce.codeplex.com

 

Follow SharePointAce on Twitter! Follow me on Twitter.


Contributor to the book:

 

Occasional Speaker at SharePoint Saturday - SharePoint Saturday

RecentComments

Comment RSS