What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: Debugging SharePoint
Select a size
This presentation reviews how to debug SharePoint via Reflection in order to gain insight into the inner workings of SharePoint as it relates to troubleshooting.
Deep Dive Troubleshooting
Methods and Tools
Working with SharePoint since WSSv2
SharePoint Server MVP
SharePoint MSDN/TechNet Forums Moderator
Using traditional developer tools in the IT pro space
Browse decompiled source
This isn’t always perfect and won’t be a 100% match with the original source, but is “close enough”
Export source to disk for later viewing (and comparison!)
Integration with Visual Studio (.NET Reflector VSPro)
Includes on-the-fly debugging support
After exporting from .NET Reflector, leverage Kdiff3 to compare between Cumulative Updates, Service Packs, and Hotfixes
Useful for identifying (unexpected) behavior changes
Multi-tab text editor
Extensive, Built-in Plugin Support and Management
Save as admin (Automatic User Account Control Elevation)
Useful for editing Hosts file
Compare files for quick differences
Syntax highlighting support
C#, ASP.NET, T-SQL, Etc…
Set IIS Application Pool setting “Ping Enabled” to False
Set-ItemProperty IIS:\AppPools\PoolName –Name ProcessModel.pingingEnabled –Value “False”
Set-ItemProperty “HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment” –Name COMPLUS_ZAPDISABLE “1”
DLL .INI Files
Place INI file in directory of DLL with the same name
[.NET Framework Debugging Control]
Save as admin:
Use this to identify issues that otherwise do not present themselves in traditional diagnostic tools (ULS, Event Viewer, Developer Dashboard…)
This is an ‘in depth’ or deep dive look into the internals of SharePoint. By looking “deep”, we’re able to see exactly what SharePoint is doing under the covers including surfacing information that we would otherwise be unaware of.
The method is to use what are traditionally a developer’s tools to look at SharePoint issues. We will be attaching to processes using the Visual Studio debugger, such as PowerShell, OWSTIMER, or W3WP and watch, step-by-step, what is happening within SharePoint. In addition, we will be tracking changes from build-to-build of SharePoint within key libraries to see additions or changes.
COMPLUS_ZAPDISABLE – do not load pre-JIT (NGEN) images (pre-compiled) AllowOptimize = 0 – do not allow NGEN