How would one enforce a strict non - "dynamic" - policy?

Posted by stormianrootsolver on Stack Overflow See other posts from Stack Overflow or by stormianrootsolver
Published on 2010-06-18T12:16:36Z Indexed on 2010/06/18 12:23 UTC
Read the original article Hit count: 210

Filed under:
|
|

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?

© Stack Overflow or respective owner

Related posts about c#

Related posts about dynamic