When running FxCop on any managed code that uses CoSetProxyBlanket you will see an error message saying the method cannot be called reliably from managed code. I’ve hit that message before was frustrated by my attempts to find an explanation on the web. Part of the reason is I’m not the most efficient searcher on the web.

Just found out about a neat way to keep track of managed object references while debugging. Check out this blog entry

When you make a WinForm TextBox ReadOnly, it aquires a distinctive look because it changes the background. Users often want the appearance of the TextBox to stay the same, they just don’t want it to be mutable. Here’s a snippet to make a TextBox ReadOnly and not change it’s appearance.

It’s somewhat frustrating to try and post code to the internet for your blog. Getting the color scheme right isn’t easy if you’re like me and don’t use a standard color scheme for coding. I prefer a very dark coding environment (inkpot) and most people don’t want to read code in that scheme.

I often delete versioned files from Visual Studio without great care for the source control impact. However I eventually have to go through and clean up the mess I made by not properly deleting the files from svn as well as on disk. When you delete a file physically but not in SVN, SVN willl declare the file missing.