Linq performance, Count() vs Any()
I just came across some very interesting information. Every used the following statement:
if (mysequenece.Count() > 0)
{
//Do something
}
The problem here is the Count() statement which can potentially be very inefficient, as it traverse the whole list to calculate a value. But we reallly don't need the exact count, in most cases we just need to know if there are any values, and hence, we can rather use Any() which is another extension method from Linq.
Upgrading Caliburn
This last week I have looked into more details on how to upgrade a Caliburn v1 project to Caliburn v2. Marco Amendola wrote a very nice post on this back in January 2010, but the Caliburn naming conventions have change a bit since then, and as seen from the checkin-ins, but hopefully not too many "Don't hate me updates" from now as Rob Eisenberg describes them
When I first dived into the upgrade, @EisenbergEffect tweeted me a short list of major/most essential changes in namings: