Visual Studio Solution Framework for Multiple Deployed Projects

Question

Scenario:

Currently, we have one solution that supports a single deployable object, the WinForm / WPF client, this solution has a level architecture with projects representing different levels (Data, Business, UI). We will introduce other deployable objects such as LiteClient, server, and RIA.

We are considering a restructuring, where we will have several solutions, one for each deployable enterprise (Client Solution, Server Solution, RIA Solution, etc.), these solutions will share various projects, for example, a data-level project. This, in fact, is a shared, one-stop solution recommended by the Microsoft P & P team ( http://msdn.microsoft.com/en-us/library/Ee817674(pandp.10).aspx )

Question:

Besides the administrative overhead of this approach, are there any serious goths of the world awaiting us if we accept it.

Answer 1

This is a reasonable and normal approach. After all, a Visual Studio solution is simply a collection of projects with deployment information.

To reduce possible dependency issues, make sure you use a build server (TFS or otherwise) that takes care of compilation and deployment.

Answer 2

If you changed something within the framework of common projects, you need to check if they have violated dependent projects. If you save these projects in separate solutions, you should remember that they will recompile them every time you change common projects.

This is the flaw that I see.