Hi,
You are confusing two things, the logical design ( classes,struct , etc )
and physical ( .dll , .exe )
IMO at this point you should concentrate in the first, how to implement the
classes, you said that you can group them , maybe this can be represented
with one abstract base class that implement (or define) the common
functions.
You have to define an abstract instrument from where all the groups derive
from. This would allow you to create a collection of instruments. If as it
seems from your post an user can select what instrument it can choose from
then you could for example declare all of them in an assembly, then you
could using reflection get all the classes that implement a giving interface
(IInstrument).
Depending of how big your code is you could put them in a single dll. If
not possible remember to declare the shared declarations ( Interfaces, etc)
in a single dll and make all the other dlls reference this common one.
Take a look at
http://www.yoda.arachsys.com/csharp/plugin.html
cheers,
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"Adine" <ad********@yahoo.com> wrote in message
news:ae********************@magma.ca...
Hi,
I need to develop a program to control electronic instruments. We have so
many different instruments but we can group them. Each group has some
common functions. When user choose an instrument, the other instruments
may not be needed at all. So I was thinking if I want to write one
executable file and put all instruments functions in it, I will have a
huge file and user just needs 2% of that. So I thought that could be
better to have an executable file for each instrument. But we need a form
to choose them, plus they are some common functions in a group or there
are some functions to link two different instruments. So each executable
file should be individual but not completely (not in separate solution).
Now how should I design it? Should I use N-Tier solution?
Thanks