when projectreference casing and file system casing differ project.assets.json gets regenerated

[kingerja]

NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):
msbuild 15.9.21.664
using msbuild /t:Restore

VS version (if appropriate):
15.9.6

OS version (i.e. win10 v1607 (14393.321)):
win10 v 1809 (17763.253)

Detailed repro steps so we can see the same problem

1. File system has directory structure like.
   Foo\Bar\ProjectA.csproj

2. Project B has project reference foo\bar

3. msbuild /restore Foo\Bar\ProjectA.csproj
   copy off the project.assets.json file from projectA.csproj.

4. msbuild /restore projectB.csproj
   windiff new ProjectA.csproj project.assets.json with the copied off one.

Note the casing different which breaks incremental builds.

casing.zip

[anangaur]

Related issue for lock files: #7840

[nkolev92]

Casing.zip

I have another scenario that's broken. In my case, standard restore evaluation and static graph restore are self-consistent, but don't work when run in combination. Example, msbuild /t:restore and msbuild /t:restore /p:RestoreUseStaticGraphEvaluation="true" does not no-op.