No updates to the debugger last night because I was in the office until far too late and far too tired to be bothered afterwards. There's a nagging voice at the back of my head that says "This debugger might be more useful if you could see what line of code you are currenly broken on" and so I really will get that working soon. I'll also send the latest version of the #Develop addin to the developers so they can see where I am. I need to think about how I'm going to structure my internal code, which I have a horrible feeling will mean using a singleton as a global variable, but since we're only talking about a thin wrapper around my library code it's not too much of a hassle.
I've also been working on the website for the debugger and, more importantly, the work I've done to understand the APIs. I'm aiming at having resources for how debuggers work under both the CLR and Win32, how to actually use debuggers including tips for Visual Studio and WinDbg and I'm also finding that I need to cover testing as well since you can't debug something unless you know it goes wrong.
What other blogs are saying about this post.
10:31:42 AM 
|
