dotnet/msbuild

Detect and log dev drive at the start of build

Open

#12,108 opened on 2025年7月3日

GitHub で見る
 (0 comments) (1 reaction) (1 assignee)C# (5,062 stars) (1,364 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.