dotnet/msbuild

Use Microsoft.IO.Redist in FileUtilities on net472 instead of custom methods

Open

#13078 opened on Jan 21, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (5,062 stars) (1,364 forks)batch import
backloghelp wantedtriaged

Description

The note in the targets file that sets the variable says these optimizations are relevant for net4.6, we're beyond that so we might be able to use the Microsoft.IO redist ones instead.

  1. decouple FEATURE_LEGACY_GETCURRENTDIRECTORY and FEATURE_LEGACY_GETFULLPATH from net472
  2. conditionally compile FileUtilities with using Microsoft.IO
  3. don't compile the custom methods outside of net35 taskhost project

Contributor guide

Tech stack
csharp
Domain
build system
Issue type
refactor
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C#conditional compilationdependency management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Locate the targets file that defines FEATURE LEGACY GETCURRENTDIRECTORY and FEATURE LEGACY GETFULLPATH. Identify the FileUtilities class and the custom methods to be replaced with Microsoft.IO.Redist equivalents. Check the Microsoft.IO.Redist package for available methods. Propose changes to conditionally compile FileUtilities to use the Microsoft.IO namespace instead of the custom implementations.