Dick,

Keep in mind that every project compiles to a .DLL (or .EXE in the case of a WinUI) and you want to keep these small and functionally specific.

For example ... my application uses lots of DataSets. I have various projects for the different kinds of DataSets in order to break up the .DLLs into manageable pieces (not only for deployment, but for better organization of my app). In other words, I'll have projects called DataSets.Incident, DataSets.Personnel, etc. Each of those projects can contain multiple dataset classes that pertain to each function (I might have five dataset classes in the DataSets.Incident project, three dataset classes in the DataSets.Personnel project, etc...) Hope this makes sense to you ...

>>There seem to be some pathing issues with regard to IIS in a web project.<

What pathing issues are you referring to?


~~Bonnie


>I haven't seen a significant discussion on the suggested layout of projects/solutions in VS.NET. For example, should I include project specific classes inside the project itself or should I create a new solution that contains all of my special classes and then include it as an assembly?
>
>There seem to be some pathing issues with regard to IIS in a web project.
>
>Does anyone have a suggestion as to where to look for thoughts or examples of this?
>
>Dick Harrold