Best Visual Studio solution / project structure for a client / server project with a common model

Question

I'm curious what is the preferred way to structure an application with an executable client program, an executable server program, and a common model in solutions and projects (using Visual Studio and C #). Being used for Java development, I initially looked at projects as packages and defined a project for every package I developed.

The result was a solution with six projects (one for the model, one for the server and four for the client), which in turn led to some silly dependencies, forcing me to reconsider if this is the best approach.

Now I plan to restructure the solution for three projects: the client project, the North project and the model project. Both the client and the server will depend on the model project (in which I will also add a common interface between the client and server).

Is this the best way to structure such an application?

Also, what is the best way to reflect namespaces in a Visual Studio tree structure? (Just create a similar folder structure, for example?).

Answer 1

A 3-project solution (client / server / model) is really the norm for your scenario.

: , , . , .