* Look deeper under the hood: Reflector, Sql Profiler, Debugger, VS Tracing, Tracing File, Log Files, Windows Event Logger...
* Compare with working version: svn, different version of database...
* if crashes on create, debug the constructor
* Always Set Stop On Exception While Doing Debugging in Visual Studio 2005 or 2008
Menu -> Debug -> Exceptions... -> Tick all the check boxes
* Attach to w3wp is unstable. F5/debug may show you more debug info
* Debug window "Call stack", "Immediate" and "Disassembly" are very useful.
* Use break point's hit count, stop condition and when hit (you can print when the statement is hit)
--Crm--
* Turn on DevErrors in web.config
* For Crm client, run the diagnosis tool.
No comments:
Post a Comment