On windiffing 1.4 with 1.5 I found loads of instances of code like this:
List<Something> mySomethings = Manager.GoGetSomething();
having been replaced with:
var mySomethings = Manager.GoGetSomething();
I am really curious about the reason for this change - because to me it looks like "bad" code.
I thought that var was mainly intended for Linq queries and other scenarios where you dynamically create an anonymous type. My understanding is that the compiler infers the type - and it's simply a convenience for having to type out loads of class definitions - however, using it (like the above example) to store data from methods returning nicely typed collections seems wrong to me.
However this change from Lists to var seems to be implemented quite consistently throughout v1.50 - and with the quality of the code behind nop I am pretty sure that there must be real reason for changing this throughout...
Great work on the 1.50 version btw!