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# (1,364 forks)batch import
Good First Issue

Repository metrics

Stars
 (5,062 stars)
PR merge metrics
 (Avg merge 11d 7h) (125 merged PRs in 30d)

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

Research direction
Inspect the implementation of the similar feature in dotnet/msbuild#10151, then add dev drive detection similar to that pattern.
Tech stack
csharp
Domain
build systemdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75