design and maintenance issue

[vcllvc]

I am running into a design and maintenance issue. Any comment can be helpful.

I am redesigning a auto insurance company quoting system in c# and basically start from a scratch. Each vehicle type will have different pricing, of course. I have a base class – Quote and different vehicle quote type will derived from the Quote, such as SUVQuote, SedanQuote, etc.

Ok, here is the problem.
The company has many different (the images and product names) web sites selling the same insurance products in different names and price.

Should I generate a single assembly dll which contains all the base class and derived classes and deploy it to every site.

Or should I separate the base class and derived classes into different dlls, then copy the base class dll to the GAC and the derived class dll into the site.

This is my first project that needs to handle such situation, so any suggestion can be very helpful.


Does anyone have any suggestion? Thanks in advance.

 

[BobRodes]

You might want to run this by the C# forum, since it's a question having to do with practical specifics of .Net deployment. However, also, I'd like to mention that having different quote types deriving from a base quote only makes sense if, to use your example, sedans and suv's have some differences in state and behavior associated with them.

HTH

Bob