One advantage to breaking your code up into one EXE and several DLLs is to give you the flexibility of deploying your WinForm app on the Web. Each DLL can be downloaded on demaind, much like an HTML-based app that's downloaded page by page. If you stick all the code into one EXE, then it is a much larger download for the user up front.

>This is one of those 'where does the code go' type questions...
>
>I have a WinForm app with many classes that I've built. A customer class, a user profile class, a deduction class, etc. Each class has a bunch of properties related to that class, some methods, etc.
>
>At the moment, the classes are directly part of the main project. (The top of each class file has a namespace referring to the main application name).
>
>My question is whether it makes more sense to build each class as a separate DLL/project, and then add each class as a reference in my 'main' WinForm app....or to just do what I'm currently doing (putting the class code right into the project).
>
>I don't know if it's just a 'packaging' and file distribution-type decision, or if there's more to it than that.
>
>Most of these classes would never be used by another application [our application is a single commercial product], though a small handful might down the road.
>
>Thoughts?
>
>Thanks,
>Kevin