How would one enforce a strict non - "dynamic" - policy?
- by stormianrootsolver
We are going to introduce .NET 4.0 and I'm VERY afraid of people using dynamic in the future, thereby destroying code quality, Intellisense capability and type safety.
What would be the best way to enforce a strict non - "dynamic" - policy? Is there a way to turn off the "dynamic" - keyword in the compiler?