dotnet / dotnet/msbuild

Please consider exposing more of FileUtilities API

Open
#2,747 0 comments 0 reactions 0 assignees View on GitHub
triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 8h
Merged PRs (30d)
141

Description

I am writing a compiler task, targeting both Windows and Linux, and, from looking at MSBuild sources, realize how many of very important path massaging APIs are internal. Only FileUtilities.GetFolderPath is in fact exposed as public. I have to essentially recreate (inefficiently) such functions as NormalizePath(), which is highly optimized, and a whole host of convenience helpers, such as IsTrailingSlash, DeleteNoThrow etc etc.

Please consider exposing as much of these as reasonable, and perhaps other utility API from Shared/, through the Microsoft.Build.Utilities.Core assembly.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.