microsoft.netframework.referenceassemblies.net452 has incorrect version of System.Runtime

[weshaggard]

I'm using the microsoft.netframework.referenceassemblies version 1.0.0-preview.2 and when building against net452 I end up with the warning:

 C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Runtime". Check to make sure the assembly exists on disk. If this reference is
required by your code, you may get compilation errors. [D:\adp\azure-sdk-for-net\sdk\resources\Microsoft.Azure.Management.Resource\src\Microsoft.Azure.Management.ResourceManager.csproj]

detailed log info:

  Primary reference "System.Runtime". (TaskId:22)
C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Runtime". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\adp\azure-sdk-for-net\sdk\resources\Microsoft.Azure.Management.Resource\src\Microsoft.Azure.Management.ResourceManager.csproj]
          For SearchPath "{TargetFrameworkDirectory}". (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\System.Runtime.winmd", but it didn't exist. (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\System.Runtime.dll", but it didn't exist. (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\System.Runtime.exe", but it didn't exist. (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\Facades\System.Runtime.winmd", but it didn't exist. (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\Facades\System.Runtime.dll",
  			but its name "System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
  			didn't match the expected name "System.Runtime". (TaskId:22)
          Considered "D:\adp\azure-sdk-for-net\restoredPackages\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\Facades\System.Runtime.exe", but it didn't exist. (TaskId:22)
          For SearchPath "{RawFileName}". (TaskId:22)
          Considered treating "System.Runtime" as a file name, but it didn't exist. (TaskId:22)

After digging into this more it appears that for some reason microsoft.netframework.referenceassemblies.net452 as an incorrect version of System.Runtime which causes this issue.

I diffed this System.Runtime vs what is installed with VS and there is a different assembly version:

C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\Facades\System.Runtime.dll

Has version 4.0.10.0

\microsoft.netframework.referenceassemblies.net452\1.0.0-preview.2\build\.NETFramework\v4.5.2\Facades\System.Runtime.dll

Has version 4.0.0.0

Which is what I believe is causing the warning.

I've not figured any way to suppress this warning as it doesn't cause any breaks for me other then my warnaserror checks fail. So any potential way to suppress this would also work for my case.

[livarcocc]

@weshaggard I am not sure this is the right repo for this bug. We do not own that package.

@dsplaisted can you direct this issue to the appropriate owner?

[dsplaisted]

We don't really have a good repo to file issues with the .NET Framework targeting packs, so I told Wes to file this here (mainly since we're tracking another issue in this repo already.

I've let Nikola know about both issues.

[weshaggard]

@NikolaMilosavljevic any update on this issue? This is still causing lots of warnings and noise in our builds and I don't have any good way to workaround it.

[NikolaMilosavljevic]

@NikolaMilosavljevic any update on this issue? This is still causing lots of warnings and noise in our builds and I don't have any good way to workaround it.

The fix is available and pending release. Hopefully in the next few days.

[XiangyuL-Microsoft]

I reach this thread by searching online. I've encountered the identical issue. Is there any update? @NikolaMilosavljevic.

Thank you very much.

[dsplaisted]

This should now be fixed with the 1.0.0 release of the packages.