I am always pulling out the Unity assemblies. Maybe it is just because I am lazy, but I really can’t be bothered rolling my own dependency injection and mapping framework!
Even though this sounds like a really simple thing, what if you do not know the name of the controls, and you do not want to have to add a bit of code that you, or another may developer may forget to every piece of code with a timer in it.
LINQ is syntactical sugar for extension methods and lamda expressions. To understand LINQ, it is important to first grapple with these concepts.To begin, let's look at a simple and somewhat common scenario.
Staring from the original Command Line Parser v1.0 code, I wanted to be able to add multiple commands, or even nest commands. The result is a nice simple commanding architecture conducive to creating multiple commands.
