Visual Studio项目/解决方案结构是否有最佳实践? [英] Is there any best practices for Visual Studio Project/Solution Structure?

问题描述

我在这个问题上看到了很多不同的看法，所以我想出了这方面是否有首选的方法.

I've seen a lot of different takes on this subject so I figured if there's a preferred way on this.

关于针对同一解决方案的多个解决方案，是否有关于设置Visual Studio项目和解决方案的最佳实践?

Is there any best practices on how to setup Visual Studio Projects and Solutions in regards to multiple solutions for the same solutions?

例如: 假设我有一个任务，需要一个Web应用程序，一个控制台应用程序和一个共享的业务逻辑库.

For example: Let's say I have a task that calls for a web app, a console application, and a shared business logic library.

在我职业生涯中的某些时候，我已经通过1、2和3解决方案看到了这种情况.这是一个简单的例子；但是，如果项目数量增加，该怎么办?何时将其合为一体或分开?

I have seen this situation in a 1, 2, and 3 solutions at some time in my career. This is a simple example; however, what if number of projects grows? Is there a line when to keep it in one or break it apart?

推荐答案

实际上，在回答类似问题的问题中写了一个简短摘要在StackOverflow上.

Indeed, there are some guidelines for this sort of setup on MSDN. I wrote a short summary in my answer to a similar question on StackOverflow.

这篇关于Visual Studio项目/解决方案结构是否有最佳实践?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！