OK, let's try again. <g>

A solution contains many projects. Each project will compile to a DLL. All except the startup project, which is the one you want to compile to an EXE.

So, your SalesWindow.DLL could have multipile .cs files in it. Maybe a SalesForm.cs and any number of other .cs files with supporting classes in it. You don't have to have only one class per .cs file either ... one file can contain many classes.

Does this help?

~~Bonnie



>Sorry, I am not explaining myself correctly. This is not about business logic concepts. It is about files, Projects and Forms (the actual .cs files).
>
>I want:
>
>saleswindow.dll
>customerwindow.dll
>orderwindow.dll
>
>Is each a separate Project (Sales Project, Customer Project, Order Project)? I need them separate for valid reasons.
>
>I ask because I do not need Program.cs in every DLL. I don't need all of the extra folders the Project creates.
>
>What is the most simple way? Or are Projects the only way?
>
>Thanks guys, don't worry about the business concepts organizational logic.