One of the really cool things about working on and having the community use your tools is sometimes you get really great feedback and suggestions. Recently Heiko Hatzfeld from Microsoft PFE suggested we include method parameter or argument details into the output details produced by SNAP when it takes a snap of a process.
So have you ever heard this â€œThere is Nothing in the ULS Logsâ€ or better (worse) yet you have experienced it. Yea me too, itâ€™s a real bummer and your next step is to typically crank up the ULS logging verbosity and crossing your fingers. Sometimes you get lucky and sometimes you donâ€™t â€“ so where next? I have found myself attaching a debugger and looking at the managed exception messages that trail across the debugger window while I reproduce the problem and sometimes these are enough to either provide a line of investigation or possibly the answer to my issue.
As a follow up to my previous post When Page Output Caching Does Not OutputI have recorded a video which actually walks you through the steps and issues which I documented in this previous post. So for those of you whom donâ€™t like to read all that much you may watch this video and/or refer back to my previous post on the same subject.
Recently I left Microsoft where I worked for almost 15 years and where about 10 of those years were spent in Escalation Services where my daily routine was debugging failing or faulting applications. This all began with user and kernel mode Windows processes and then once the .Net Framework shipped I move to the ASP.Net and CLR teams and began debugging more managed processes. Normally customers would send my team crash dumps or memory dumps of the offending process(s) and we would use tools such as WinDbg or CDB to dig deeper into the process to determine what was happening. There are several challenges when doing this type of work and one of the most painful is locating and referencing the correct symbols files (*.pdb).
Continue reading Making Debugging a SNAP
SharePointâ€™s Page Output Caching can offer a massive performance boost to publishing sites but only when its working and working correctly. One of the problems I have seen is when some administrators turn on Page Output Caching they just assume it works. While this may be the desire and in most cases it may just work for you I would suggest you verify; and I donâ€™t mean hit the site with the browser to see if it speeds up.
This post is about troubleshooting SharePointâ€™s Page Output Caching. Now if you donâ€™t use Page Output Caching or yours is working just fine you are the â€œMaster of your Page Output Cachingâ€ â€“ as for the rest of us we will likely need to put on our troubleshooting hat and dig a bit deeper. I find troubleshooting anything is allot easier if you know a little about how the component you are troubleshooting operates and how it is suppose to work.