Here's a little holiday cheer for you all. Or, at least for you all in Commonwealth countries. static object M<T>(T t) where T : struct { return t; } int ii = 10; int? jj = 20; object xx = ii; object yy = jj; System.ValueType zz = ii; IComparable...

Consider the following scheme: I have some client software which I sell. When the client software starts up for the first time, it obtains a “token” from the user. The token string can be anything; the user can choose their name, their cat’s name,...

What happens here? class Animal { } class Mammal : Animal { } class Giraffe : Mammal { } class Reptile : Animal { } … static void Foo<T>(T t) where T : Reptile { } static void Foo(Animal animal) { } static void Main() { Foo(new Giraffe()); }...

As you probably know, there are two ways to write a LINQ query in C#. The way I personally prefer is to use the “query comprehension” syntax: from customer in customerList where customer.City == "London" select customer.Name Or you can, equivalently...

I thought it might be interesting for you all to get a precise description of how exactly it is that we determine when it is legal to put "in" and "out" on a type parameter declaration in C# 4. I'm doing this here because (1) it's of general interest...