hi, at first thanks for reading so far... ;-)
indeed this is an old stuff but the new stuff is an old stuff only presented in a different way.
This framework does not use any special GUI technology, it does not communicate with other components using WCF. It uses plain old ThreadPool for asynchronous operation and a service container.That's why in my opinion the .NET 2.0 is enough.
Combining components together and communicating using asynchronous messages you create a village and its residents or how a programmer would say - a state machine. The village can turn into a small town, a small town can turn into a metropoly. The state
machine can grow unlimited but their components still work loose coupled, independently.
The simplicity of this framework and easy usage pattern are strength of this framework. The drawback is - you create many classes for each use case (however actually I use a code generator to generate them) but the real advantage is when you work in a team,
you don't need to merge big, fat objects but you copy the whole components, messages and commands from one place to the other.
It really works :-)