In this post I am going to write the points about the three type of the iable , and Dynamic. Most of the developer not able to get what is between this three kind of iable.
Reference : Code Project
|Can able to store any kind of value, because is the base class of all type in .net framework.||Can able to store any type of the iable, similar to old VB language iable.||Can able to store any type of value but it require to initialize at the time of declaration.|
|Compiler has little information about the type||Compiler doesn't have any information about the this type of |
|It's compiler safe i.e compiler has all information about the stored value, so that it doesn't cause any issue at run-time.|
|type can be passed as function argument and function also can return type||Dynamic type can be passed as function argument and function also can return type|
type can not be passed as function argument and function can not return type. This type of iable can work in the scope where it defined.
|Require to cast |
Allows to perform operation of given type once it get cast any user defined or primitive data type. iable to original type before using it. So this assigning to type and converting to original type called as Boxing and Un-Boxing for value type and for the reference type its casting of types. It's actually increasing the overhead when we do this both operation.
|Casting is not require but you need to know the property and methods related to stored type||No need to cast because compiler has all information to perform operation.|
|Cause the problem at run time if the stored value is not get converted to underlying data type.||Cause problem if the wrong method or property accessed because all the information about stored value is get resolve only at run time||Doesn't cause problem because compiler has all info about stored value.|
|Useful when doesn't have more information about the data type.||Useful when coding using reflection or dynamic language support or with the COM s, because we require to write less amount of code.||Useful when getting result out of the linq queries. In 3.5 framework it introduce to support linq feature.|