dotnet/msbuild

Detect and log dev drive at the start of build

Open

#12,108 创建于 2025年7月3日

在 GitHub 查看
 (0 评论) (1 反应) (1 负责人)C# (5,062 star) (1,364 fork)batch import
Good First Issue

描述

Summary

dev drive has big impact on local build time for larger projects, due to file io speed improvement. Information whether customers used it during a build is useful for investigations.

Background and Motivation

e.g. recently we looked at a project that took 10mins of copy operations and when moved to a dev drive it took ~2

Proposed Feature

Probably can be implemented in the same way as https://github.com/dotnet/msbuild/issues/10151

Alternative Designs

No response

贡献者指南

技术栈
csharp
领域
build systemperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
C# programmingMSBuild internalsWindows file system APIs
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Review the referenced issue https://github.com/dotnet/msbuild/issues/10151 for a similar implementation pattern. The implementation likely involves checking for Windows Dev Drive using APIs like GetLogicalDrives or QueryDosDevice. Look for existing helper methods in the MSBuild codebase for platform detection. The log should be added near the beginning of the build process, possibly in the BuildManager or RequestBuilder classes.