John & Derek,

We break up our layers/tiers even further. And the projects are also broken down by functionality:

Business would consist of:
MyCompany.Business.Personnel
MyCompany.Business.Incidents
MyCompany.Business.Inspections

DataAccess would consist of:
MyCompany.DataAccess.Personnel
MyCompany.DataAccess.Incidents
MyCompany.DataAccess.Inspections

DataSets would consist of:
MyCompany.DataSets.Personnel
MyCompany.DataSets.Incidents
MyCompany.DataSets.Inspections

WinUI would consist of:
MyCompany.WinUI.Personnel
MyCompany.WinUI.Incidents
MyCompany.WinUI.Inspections

We also have a WebService layer, with each area of functionality having it's own WebService class. So, there's only one WebService project (one .DLL), consisting of multiple classes.

~~Bonnie




>>In developing VS C# applications, are you guys compiling all window forms into your EXE or just some (the rest would be external to the EXE)?
>>
>>How are you managing compiling the external forms to DLL files? Are you using Visual Studio to create the FORM.CS and FORM.DESIGNER.CS -- and then how are you converting them into DLLs? Is there an easy way of doing this? I have 14 3" books (that cost me $750) and I can't find one simple answer (sorry to be venting).
>>
>>Obviously the second paragraph would have no answer if you compile all windows into your EXE.
>>
>>Thanks in advance and happy belated New Year to everyone.
>
>The way I do it is to create four projects in a solution. MyApp, MyCompany.Windows, MyComapny.Business and MyCompany.Data.
>All of my windows forms go into the MyCompany.Windows namespace and compile into a dll called MyCompany.Windows.dll, all business objects into MyCompany.Business and all data access into MyCompany.Data.
>
>The Main projectt references the other three so it can access the resources in the dlls.