Organize Projects and Assemblies

[bstrike]

I am certain, this question was asked plenty of times before, but I
could not find a satisfying answer. So please apologyze my lack of
knowledge. We are fairly new to .NET and C#.

We would like to create a new ERP System with C#.NET that will contain
Windows Forms, Web Forms, UserControls, Resource files for multilingual
environments, and many Code-Behind classes as well.

Our first thought was an organization like this:

Solution <Abbreviation for Company Name>
|_Common Folder
| |_User Controls (Folder)
| | |_Domains (Folder)
| | |_Entities (Folder)
| | |_Controls & Classes
| |_Classes (Folder)
| |_Code
|_Product 1 (Project)
| |_Windows Version
| | |_Forms
| | |_Classes
| | |_Code
| |_Web Version
| | |_Forms
| | |_Classes
| | |_Code
| |_Language based Objects
| |_Ressource Files
|
|_Product 2 (Project)
| |...
|_Product 3 (Project)
| |...
....
Assuming this kind of structure would be durable could we
still refer to a namespace-setup like Company.Product.Forms,
and Company.Common.Controls throughout all projects within
the soulution? And, what would we have to consider to maintain
different realases/versions of thesame product/project?

What would be the down side of this setup?

Thanks, your input will be very much appreciated.

 

[Robbe Morris [C# MVP]]

I'd think you'd want to keep your UI layer
for the web environment and the windows
environment in separate assemblies.
I work quite a bit with software families
like this and the approach in the article
below has worked quite well.

This should help with your project setup
for this type of environment:

http://www.eggheadcafe.com/articles/aspnet_how_to_create_object_oriented_applications.asp

 

[Brent]

Robbe,

thank you very much. Your feature was exactly the answer to my
questions. Thanks again and keep up the good workon eggheadcafe.com.

Brent