Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix DotnetSharedFrameworkTaskDir to not rely on DotnetBuildFromSource (…
…#8355) (#8597) After #8338 we saw a build error in a dotnet/runtime build job that tries to validate source-build but still uses the non-source-built arcade packages: ``` /__w/1/s/artifacts/source-build/self/src/src/libraries/ref.proj(68,5): error MSB4062: The "CreateFrameworkListFile" task could not be loaded from the assembly /__w/1/s/artifacts/source-build/self/package-cache/microsoft.dotnet.sharedframework.sdk/7.0.0-beta.22064.25/sdk/../tools/net6.0/Microsoft.DotNet.SharedFramework.Sdk.dll. Could not load file or assembly '/__w/1/s/artifacts/source-build/self/package-cache/microsoft.dotnet.sharedframework.sdk/7.0.0-beta.22064.25/tools/net6.0/Microsoft.DotNet.SharedFramework.Sdk.dll'. The system cannot find the file specified. ``` This is because the non-source-built arcade packages use netcoreapp3.1 libraries instead of net6.0, but we're still setting DotnetBuildFromSource=true in those builds. Instead of using DotnetBuildFromSource to switch between libraries we can check for the existence of the net6.0 folder which works in both scenarios. Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
- Loading branch information