dotnet / dotnet/msbuild

GenerateMSBuildEditorConfig task breaks incremental build on Windows when using different casing paths

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

Description

**Version Used**: 17.10.4+10fbfbf2e

**Steps to Reproduce**:

1. Have a dummy under X\x.csproj (sdk)
2. Build from some y\dirs.proj with ProjectReference="..\X\x.csproj" -> full build
3. Build from another z\dirs.proj with ProjectReference=..\x\x.csproj" -> will trigger full build because path is invoked with lower case "x\"

**Diagnostic Id**:
Using "GenerateMSBuildEditorConfig" task from assembly "Current\bin\Roslyn\Microsoft.Build.Tasks.CodeAnalysis.dll"

Input file "x\obj\amd64\LegacyUri.UnitTests.Core.GeneratedMSBuildEditorConfig.editorconfig" is newer than output file

**Expected Behavior**:
No recompilton CoreCompile should happen on Windows because the paths are identical, just casing is different.

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.