At work, recently I attended an excellent presentation given by a colleague where we talked about Debugging in general (across both Managed and Unmanaged code), and what the various categories are, and various tools at ones disposal, etc. I thought this post from Rico on how to find GC leaks was quite timely for that topic.
[Listening to: City of Blinding Lights - U2 - How to Dismantle an Atomic Bomb [Bonus Track] (05:48)]
Similar posts to check out:
- February 3, 2009 -- Exceptions Management (or lack of it) (0)
A good example of what not to do. ... - November 13, 2006 -- DragMove (0)
Did you know there is a new method called DragMove which is part of the Window class and allows you to move the window using a mouse? I certainly did not - till now. This is part of .NET 3.0, specifically part of WPF and . Here is an example from the SDK:protected override void OnMouseLeftButtonDown(MouseButtonEventArgs e)
{
base.OnMouseLeftButtonDown(e);
// Begin dragging the window
this.DragMove();
} ... - January 3, 2006 -- Writing High-Perf. Managed Apps? (0)
If you are writing high-perf. managed applications, all the old-world advice from the days of good old COM is still valid. But you do need to think of a few other things such as how the CLR JIT would change things, or the Exception Handling, or Threading and syncing up, or possibly the GC and Allocation Profiles? While this MSDN article is old (now), it still is excellent Food for Thought when it comes to writing high-perf. apps....
Tags: .net
