http://www.memorymanagement.org/

   This is a weird compiler error, but it simply means you're trying to assign a value to a method, and as you know, that's a no-no. Don't ask how I stumbled across this error
Recommended reading:

   And good ol' channel 9 has a video about the LINQ project (feature Anders Hejlsberg).

   I hadn't heard of this project before, but the concept seems quite cool. Back in the days of the 1.0 framework I had written a framework which allowed me to query metadata of objects on the managed heap of my process (I could search for strings, etc.); it seems as though I should have continued down that path, I guess...

I'm sure you're all aware of the WMF vulnerability and all the hoohaw surrounding it as a potential backdoor implanted by Microsoft. Mark, in his latest post (as of this posting) gives a wonderful analysis as to why he believes it's not a backdoor by Microsoft. What I find most interesting about this post, however, is the inside look given by him into the vulnerability itself; most of us simply download the patch by Microsoft for the 'bug' and call it a day - but it's interesting to look deep into why the vulnerability existed in the first place and how some 'flaws' may actually be, originally, simply a feature.

I really get a kick out of some of the stuff Mark comes up with...

   At work we're in the process of installing Vista and the latest and greatest bits from Microsoft onto a Dell we have laying around; and it's quite apparent to me that my fascination with WCF is going to mean a lot of code writing (which I'll be posting here), I'm hoping to become more and more focused on it as it's really what gets me the most excited about the new OS from MS. Here is a homepage for the WCF courtesy of a blog post by Don Box, it's someplace I'll be frequenting.  

I normally don't talk about our company much on this blog, but I thought it might be interesting for some to see our new office building.