Question : Visual Studio 2008 workflow & architecture

Hi all,

I am working on a project in Visual Studio 2008. There are 3 separate Windows Forms apps which use a common set of classes, written specifically for and shared between these exe's. I have little experience with Forms apps and moderate experience with ASP.NET dev in VS2008.

Two questions:

What is the best way to arrange the projects from a software architecture perspective? One core dll and 3 separate exe's for the user interface?

What is the best way to arrange the projects from a visual studio workflow perspective? For example, If I change a property name in the core dll, can this propagate to all child Windows Forms apps?

I hope my description is clear enough, please ask if you need more info!

Thanks.

Answer : Visual Studio 2008 workflow & architecture

i would go like this:

solution1
    project1 (Form1)
    project2 (Form2)
    project3 (DLL)
    project4 (SetupProject)

if you change the property name it woluldn propagate to the child apps. But as long as you are in a solution i think you can make a "global" rename.