Few weeks ago, I did presentationt to my QA team about how they can found elusive bugs faster and easier. I think that this information can be useful information to any one who tests a Windows application. Please feel free to share your opinion on this PPT.

Probably, many of my co-workers are adding these kind of information into their blogs. but I decided to make my own list again. so if you want to see, check “ Known debugger issues in VS8 Beta1 ” article.

In most times, while I do dogfood/test VisualStudio 2005, I put them under debugger to monitor several things... - First Chance AV - Unhandled Exception - Userbreaks from System to process under debugger - Appverifier(a tool which is part of Application Compatibility Toolset) notification...

Well, while we are moved to this weblog, the link of my document is just gone from gotdotnet. and I got many mails from people about whether the latest document is. so I moved it on my weblog. it is live!!! whenever there is any new issues from customer, I updated it. so please enjoy it. if you want...

Sometimes, we are seeing random hangs or crashes with our testing product. well when we actually look into the post issue state, in many cases it is not easy to understand what causes the problem. One of the reasons not to see the cause is because the errornous situations are already dealt automatically...

Some times, you get frustrated because your code doesn't work when it calls methods from other people such as framework. also you don't have source code of the methods. so, even with the reference, it is not easy to understand what is wrong. Well then, open the assembly and look into the IL code with...