Skip to content

Make VBCSCompiler pipe name insensitive to casing of the path#75852

Merged
jjonescz merged 3 commits intodotnet:mainfrom
jjonescz:75714-PipeName
Nov 12, 2024
Merged

Make VBCSCompiler pipe name insensitive to casing of the path#75852
jjonescz merged 3 commits intodotnet:mainfrom
jjonescz:75714-PipeName

Conversation

@jjonescz
Copy link
Member

Resolves #75714.

@ghost ghost added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 11, 2024
@jjonescz jjonescz requested a review from jaredpar November 11, 2024 14:22
@jjonescz jjonescz marked this pull request as ready for review November 11, 2024 14:42
@jjonescz jjonescz requested a review from a team as a code owner November 11, 2024 14:42
// of this method.
clientDirectory = clientDirectory.TrimEnd(Path.DirectorySeparatorChar);

// Similarly, we don't want multiple servers if the path differs in casing.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that applicable only on Windows?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any OS can have case insensitive paths, or even paths for which parts have case insensitivity.

Co-authored-by: Jared Parsons <jared@paranoidcoding.org>
@jjonescz jjonescz enabled auto-merge (squash) November 12, 2024 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The VBCSCompiler pipe name needs to normalize the path name

5 participants