Reflection

Hi,

Please refer Our recommended articles


Thanks

As with any tool known to mankind, there are valid uses and there are inappropriate uses.
You can use reflection not only to find more information about an object/class, you can also use it to invoke methods or hook up events. You can take reflection one step further and create (the technical term is 'emit') dynamic assemblies too!

As a live example, in the Export Gridview to Excel article, I have used reflection to find the contents of a gridview cell in order to get the correct control properties and their values to be transferred to Excel.

It's good to explore the potential uses of any functionality - you get a good understanding of "what it is" and also find out "why/where can this be used".

Cheers!

Hi,

Check out Reflection in Detail from dozens of Excellent Articles.

http://www.c-sharpcorner.com/Search/?sKeywords=Reflection+.net

You should not be using Reflection on assemblies in general. It is intended to use when you do not have any idea about an assembly or you want dynamic decision on what class, method, or property you need.

One good example can be Visual Studio Intellisense. Based on the class you use in the Visual Studio 2010, Intellisense loads that assembly dynamically using reflection, reads its methods and properties and shows you in the available list.

Hi Deepak,

Please refer to the C# Corner article:

http://www.c-sharpcorner.com/UploadFile/harishankar2005/Reflectionin.NET12032005045926AM/Reflectionin.NET.aspx