您将如何组织 .net/我们面临的问题中的文件夹结构
我们将文件夹结构分为客户端层和服务器端（WPF前端 和 WCF 服务器端）除以解决方案文件夹。但两者都位于相同的解决方案下。项目数量增加了很多，现在我们在同一解决方案中拥有大约 22 个项目。 即使对于正常的构建也需要很长时间..我怎样才能避免这个问题。
我建议将解决方案分为服务器和客户端，但团队想要调试，所以他们还没有准备好。所以需要一个解决调试问题的解决方案。或者是否有任何特定的指导来组织项目的正确文件夹结构
We have divided our folder structure into Client tier and the server side( WPF front end
and WCF server side) divide by the solution folders . But both lie under a same solution .The projects has increased a lot and now we have around 22 projects in the same solution . Even for a normal build it takes ages.. How can i avoid this problem .
I suggusted dividing the solution into server and client But team wants to debug so they are not ready . so need a solution which also solves the debugging issue. Or is there any particular guidance for organizing the correct folder structure for the project
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可以创建多个解决方案。
一种包含所有项目，另一种用于客户端开发，仅包含客户端开发所需的项目等。
所有解决方案都位于同一“根”文件夹中。这对于添加项目和版本控制来说更容易。
项目可以“属于”多个解决方案，只要同一解决方案中存在对其他项目的引用即可。
您唯一需要记住的就是向所有相关解决方案添加一个新项目。
例如，我们有以下解决方案
You can create several solutions.
One that includes all projects, and one for client development that includes only the projects needed for client development, etc.
All solutions are in the same "root" folder. That's easier for adding projects and version control.
Project can "belong" to multiple solutions, as long as the references to other projects exist in the same solution.
The only thing you have to remember is to add a new project to all the concerning solutions.
For example, we have the following solutions