blocks|key|354376|text|您可以右键单击解决方案资源管理器中的单个项目，并选择仅构建该项目的选项。如果在构建顺序中有任何必要的项目，它也将构建这些项目，但这允许您仅构建必要的项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|354377|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can right click on an individual project in the Solution Explorer and select the option to build just that project. If there are any necessary projects in the build order, it will build those too, but this allows you to only build the necessary items.

blocks|key|1655913|text|你的问题有点缺乏细节，但我认为崩溃只是一个工作站资源问题。只要有足够的理由拥有这么多项目，100个项目本身就不是问题，但当你达到10个以上的项目时，我希望你已经为它们建立了某种管理结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1655914|你真的需要一直构建所有的100个项目吗？可以使用配置管理器关闭要生成的单个项目，并且可以使用项目总数的子集创建解决方案文件。|1655915|例如，我使用的一个企业应用程序有36个项目。除此之外，我们还有多个解决方案文件和配置，旨在允许我们的开发人员只加载他们需要的项目和配置，以便与应用程序的给定子组件一起工作。换句话说，他们只加载了36个项目的一些子集。我们的构建服务器负责将所有东西放在一起。|1655916|我建议对您的应用程序进行一些分析，找出哪些可以合并，哪些可以划分到其他解决方案文件中。|1655917|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Your question is a bit short on specifics, but I imagine the crashing is just a workstation resource issue more than anything. 100 projects isn't a problem in itself as long as there are good reasons for having that many, but by the time you get to over 10 projects, I would hope that you have some sort of management structure in place for them.

Do you really need to be building all 100 projects, all the time? You can switch off individual projects for building using the configuration manager, and you can create solution files with a subset of the total number of projects.

For example, we have 36 projects for one of the enterprise apps I work with. Along with that, we have multiple solution files and configurations designed to allow our devs to load only the projects and configuration that they need in order to work with given subcomponents of the application. In other words, they're only ever loading some subset of the 36 projects. Our build server takes care of putting everything together.

I suggest doing some analysis on your application and finding out what you can consolidate, and what you can partition into other solution files.

blocks|key|1582846|text|它们都需要同时构建吗？如果没有，您可以进入Configuration+Manager，只选择当前需要构建的那些。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1582847|尽管在我看来，一个解决方案中有100个项目是相当多的。这真的有必要吗？你能把它分解成更小的相关解决方案吗，或者真的有这么多相互依赖的项目？|1582848|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/kwybya3w.aspx^0|L|L|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Do they all need to build at the same time? If not, you can go into the <a href="http://msdn.microsoft.com/en-us/library/kwybya3w.aspx" rel="nofollow noreferrer">Configuration Manager</a> and only select the ones you need built at the present time.

Although it seems to me that 100 projects in a solution is quite a bit. Is this really necessary? Can you break it up into smaller related solutions, or are there really this many projects that are inter-dependent on each other?

blocks|key|1654090|text|你的问题似乎更多地与解决方案的设计有关，而与VS处理100个项目的能力无关。你真的想知道你的解决方案需要很长时间的事实是不是“我的天哪，我们设计错了”的代码味道。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654091|如果"UI“程序集和”服务器“程序集之间具有1:1的关系，则它们在逻辑上是相同的，并且可以组合。|offset|length|style|BOLD|1654092|在我看来，CAB/CAG模块程序集将它们的所有依赖项放在一个程序集中是可以的。如果您打算在多个模块之间共享数据访问代码，那么将其分解到一个单独的程序集中将是有意义的。|1654093|如果你认为这种方法不适合，我们通常做的是有几个较小的解决方案，允许我们在开发期间一起在本地测试几个相关的模块，但有一个大型的解决方案，我们的构建服务器构建。这样，长的构建时间是由专用的构建机器经历的，而不是我们本地的开发箱(这对于最小的项目也是一个很好的方法)。|1654094|entityMap^0|0|0|1C|0|0|0|C|K|A|1L|K|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]|$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|M|$]]

Your question seems to have more to do with the design of your solution and less about the ability of VS to handle 100 projects. You really want to know if the fact that your solution takes a long time is a code smell for "holy crap we have designed this wrong".

If you have a 1:1 relationship between "UI" assemblies and "Server" assemblies, they are logically the same and could be combined. 

It's ok for CAB/CAG module assemblies to have all of their dependencies in one assembly in my opinion. If you intend on sharing data access code across several modules, then it would make sense to break it out into a separate assembly.

If you decide this approach isn't appropriate, what we usually do is have several smaller solutions that allow us to test a few related modules together locally during development, but have one large solution that our build servers build out. This way, long build times are experienced by a dedicated build machine, rather than our local dev boxes (this is a good approach for even the smallest of projects, as well).

blocks|key|354465|text|默认的解决方案配置“调试和发布”始终检查所有项目，并生成不是最新的项目。您可以创建自己的解决方案配置，在该配置中，您可以为您知道不需要检查的项目禁用生成选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|354466|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The default solution configurations Debug and Release always checks all projects, and builds the ones that are not up to date. You can create your own solution configuration where you disable the build option for projects that you know doesn't need checking.

I have a solution with over 100 projects. It takes a long time to build, and sometimes Visual Studio crashes during the build. How can I deal with this issue and minimize the pain? Have we gone horribly, horribly wrong somewhere?

Some background on the problem: 

We are using CAB with WPF, and each module has a ui assembly and a "server" assembly, which is really just a layer for the database. There is only one team, with about 5 developers.

I don't know how many classes or how many lines of code.

Solution with over 100 projects takes over five minutes to build

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个超过100个项目的解决方案。它需要很长的时间来构建，有时Visual Studio在构建过程中会崩溃。如何处理此问题并将痛苦降至最低？我们是不是在什么地方大错特错了？关于这个问题的一些背景：我们将CAB与WPF一起使用，每个模块都有一个ui程序集和一个“服务器”程序集，这实际上只是数据库的一个层。只有一个团队，...

问构建包含100多个项目的解决方案需要5分钟以上的时间
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问构建包含100多个项目的解决方案需要5分钟以上的时间EN