> because then a generic requirement will propagate through the whole framework. And? Why is this a bad thing? Are you trying to maintain compatibility with .N

> because then a generic requirement will propagate through the whole framework. And? Why is this a bad thing? Are you trying to maintain compatibility with .NET 1.0 for some reason? > And some polymorphism/patterns simply won't be possible. Trust me, I've encountered this problem several times Which patterns? Please demonstrate the problem.