PasswordVault.Add may fail on Windows 10

  I am slightly embarrassed by the length of time since my last blog post. But never mind, here I am again! I’ve been working on a customer issue lately where an existing Windows Store app was failing on Windows 10. Initially the app, which ran fine on Windows 8.1 was crashing when installed and…


Background Transfer API chalk and talk

On February 26th, 6pm – 8pm GMT (10am – 12pm PST) members of our Windows Store apps developer support team will deliver an online chalk and talk about how to use and debug the Background Transfer API. “ WHAT: How to use and debug Background Transfer API issues WHEN: February 26th, 2014. 10am-12pm PST WHERE:…


DebugDiag 2.0 available

An awesome update to that long staple tool in the IIS and general debugging toolbox has now been released. DebugDiag 2.0 is HERE! Go get it! Doug


CLRMD: .NET Crash Dump and Live Process Inspection

Lee Culver, a software developer on the .NET Runtime team, has shipped an awesome managed code library for anyone interested in analysing memory dumps and the internals of running .NET applications.  Known as CLRMD, this library allows you to write code that does all the kinds of stuff you do with the SOS, PSSCOR2, PSSCOR4 …

4

Microsoft Next 2012 – featuring support diagnostics!

The Microsoft Next 2012 contest recently concluded and among the finalists this year was a video by Steve Edwards showcasing some of the great work going on within Microsoft Customer Service and Support around the world to automate the collection and analysis of the diagnostic data needed to resolve customer support problems. It only lasts…


Managing source windows in WinDBG

If you make use of the source code debugging features WinDBG you may find it quite annoying the way that each time you hit a point in the debug that relates to source in a file you do not already have open WinDBG opens yet another source window. This results in lots of open source…


Tips for successful .NET Debugging with WinDBG

Here are my tips for pain free .NET debugging with WinDBG 1) Always use a 32-bit debugger for a 32-bit process and a 64-bit debugger for a 64-bit process, both to generate the dump and to analyse it. Use usermode dumps only (managed debugger extensions are not expected to work with kernel mode) and ensure…


An interesting tool for managed memory analysis–LeakShell

  A very interesting article on manager memory troubleshooting and also the introduction of a new tool called LeakShell from Christophe Nasarre. Then he has a later post in which he talks about using LeakShell in conjunction with dump files. Great stuff Christophe! HTH Doug