Yes. Read that article, and whatever else information you can find, and then decide what works best for you. This is the thing - it may be easier to specify in a config file the plugins you want to load, but that's only if your end user doesn't have to mess with it.

The down side of dynamically loading assemblies in this method is that it is impossible to know, before you load it, if it actually implements your interface. Once you load it, there is no way to unload it. That article discusses the work around, but the amount of time you feel like spending on this work around is up to you.

In my implementation, I've taken a short cut. That is, I pretty much assume that only my (good) dll's exist in my plugin directory.