Today is the last official installment in the series on reflection. If you’ve been following along, you’ve probably notice that calling code in other classes using reflection is a huge pain in the butt.
Today, we are going to take a look at a way of taking advantage of some of the benefits of reflection without having to jump through all of the hoops that reflection puts in our way. We will do this by using interfaces. This tactic works if you know ahead of time what methods and properties your class will need but want to be able to dynamically load them at runtime. A classic example of this would be plugins.
If you're new here, you may want to subscribe to the mailing list to get notifications of new post and a virtual tour of past topics. Thanks for visiting!
Related Post
Reflection – Accessing Methods
Today is the next to last installment on reflection. We will look at how to call methods and pass parameters. This is going to look a lot like what we've already done in previous sessio...
Reflection – Loading The Assembly
Recently, I received a question from a web visitor asking me to cover reflection. So, I'm going to start a series on reflection. Remember, if you have any questions you can ask me using...
Reflection -The Constructor
Remember, last week we started a series on using Reflection in our .NET applications. We've loaded the assembly already, so the next step is creating the object. Today's tutorial will show how to...
Automatic Implementation of Interfaces
It's been a while since I've posted a video on this site because I only do videos for things that are better explained by showing you how something works. Most of what we've been looking at is cod...
Reflection From a DLL and Serialization
Last week, we finished up our main series on reflection. For most people, what we covered is all they will ever need. However, there are a few other things I've needed to know due mainl...