A Quirk in List.Find()
Earlier today I was having a chat with a friend of mine, who lives in Vancouver, about finding items that are stored in generic Lists. He flicked me a code snippet that looked something like this:
List<foo> list = new List</foo><foo>(); // .. do some stuff Foo f = list.Find(delegate(Foo f) { return foo.Name == "Bar"; }); </foo>
Straight away I fired back with an update to the code which used lambda expressions instead, as I'm a fan of how concise they are 
How do you Interact with your ViewState?
There comes a time in every ASP.NET developer's life when the need arises for information to be persisted into ViewState. For the sake of this post I'm not really interested in the reasons why. What I am interested in is how.
How do you interact with your ViewState?
Extended-Precision Floating-Point Values in the CLR
While at work today I hit a problem that I've never hit before (which is quite rare these days 
), and while it was frustrating it was also good to learn about something that I never knew was a problem. If you're having some issues marshalling double-precision floating-point information through managed components to unmanaged components, or you're just interested in learning something new, then read on
Let me start by explaining the scenario: