>Hi,
>
>I want to try to create a couple of forms to be my base class forms that will be used (inherited from) by the application (or maybe future applications). For example, I can create a maintenance base form and then inherit from it for various table maintenance forms. I think that I can only do it in code (not visually); correct me if I am wrong. But my question on where to create these base UI forms. Do I create a separate solution for these base UI classes and then reference it into my application solution? Or copy the base class files into my application solution?
>
>Thank you in advance for the suggestions.
I like putting them in the same assembly and folder as the other forms but naming the base forms beginning with 'base' like 'baseMySolutionMaint' for a base maintenance form in 'MySolution' (replacing MySolution with an abbreviation for the solution)
because a base maintenance form for one solution may not be the same as a base maintenance form for another solution unless you are fortunate to share some basic functionality between all solutions then it could just be 'baseMaintForm' or 'baseSearchForm' etc.
Sometimes common forms go into a separate COMMON folder in the forms UI assembly. The UI assembly only has forms in it, bmps, controls, skins, etc.
I like separating assemblies by layer. (UI, DATA, ENTITIES, BUSINESS, PRESENTATION, REPORTS, etc)
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"