dotnet/msbuild

Detect and log dev drive at the start of build

Open

#12,108 opened on Jul 3, 2025

View on GitHub
 (0 comments) (1 reaction) (1 assignee)C# (5,062 stars) (1,364 forks)batch import
Good First Issue

Description

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

Contributor guide

Tech stack
csharp
Domain
build systemperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C# programmingMSBuild internalsWindows file system APIs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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.