Creating my own dynamic (provider like) classes: Best approach?
<p>I'm not sure if this is the best place to post this question but I can't seem to find much on it (I guess my google-foo is weak).</p>

<p>Let's say I have a website that sells products. These products go into my database, and are processed in various ways. Recently we've decided that our website wants to sell third party products as well. Each vendor is going to have an unknown way of connecting and getting / putting information.  So my approach is this: </p>

<ul>
<li>Create an interface (IVendor) that has standard product interfacing
methods for that vendor. </li>
<li>Add a linking table between products and a new vendors table </li>
<li>Store which type to use in the vendors table as a string and convert
it to a type at runtime</li>
</ul>

<p>The goal is to minimize impact on the site codebase when a new vendor is added. Instead we'd mark a product as a particular vendor, and create a new implimentation of our IVendor for that product to use.  </p>

<p>I would love any ideas as to how this could be done better, or if I am approaching this in a way that makes sense. Thanks for your help.</p>
