I am planning to use dynamic keyword for my new project. But before stepping in, I would like to know about the pros and cons in using dynamic keyword over Reflection.
Following where the pros, I could find in respect to dynamic keyword:
- Readable\Maintainable code.
- Fewer lines of code.
While the negatives associated with using dynamic keyword, I came to hear was like:
- Affects application performance.
- Dynamic keyword is internally a wrapper of Reflection.
- Dynamic typing might turn into breeding ground for hard to find bugs.
- Affects interoperability with previous .NET versions.
Please help me on whether the pros and cons I came across are sensible or not?
Certainly true in my experence.
Not significantly, but it will help.
Very slightly. But not even close to the way reflection does.
Completely untrue. The dynamic keyword leverages the Dynamic Library Runtime.[Edit: correction as per comment below]
It would seem that the Dynamic Language Runtime does use Reflection and the performance improvements are only due to cacheing techniques.
This may be true; it depends how you write your code. You are effectively removing compiler checking from your code. If your test coverage is good, this probably won’t matter; if not then I suspect you will run into problems.
Not true. I mean you won’t be able to compile your code against older versions, but if you want to do that then you should use the old versions as a base and up-compile it rather than the other way around. But if you want to use a .NET 2 library then you shouldn’t run into too many problems, as long as you include the declaration in app.config / web.config.
One significant pro that you’re missing is the improved interoperability with COM/ATL components.