Dick,

>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?

I think it's best to keep these files in a separate project. If you add all your files to a single project, you'll produce one huge DLL/EXE. Keeping the files in different projects allows you to update just one portion of the application by replacing just the necessary DLL.

The great thing about Solutions is that you can break up my code into projects, but still include each of the projects in a single solution for easy access and compilation. Each project still produces its own compiled output (EXE/DLL), and you can set up dependencies between the projects in VS.NET so that one project compiles before another project within your solution.

I also recommend placing your business objects (if you have them) in a separate project. This allows the business object project to be used from a Windows Forms, Web Forms, Web Services, etc. solution. It also helps you more clearly delineate in your mind which code should go where!

Regards,