Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix FXVersion manifest version bug #17614

Merged
merged 5 commits into from
May 17, 2021

Conversation

sfoslund
Copy link
Member

@sfoslund sfoslund commented May 13, 2021

Fixes #17567

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@dsplaisted
Copy link
Member

Actually, I hit the same thing and fixed it (I think) for 5.0.300 in #17329. So you may just want to merge the 5.0.3xx changes forward. Also take a look at the difference between the fixes, it looks like we're handling the build number differently.

@sfoslund
Copy link
Member Author

It looks like main does contain those commits but somehow the changes got lost in places (maybe a bad merge?). I'll fix the build difference but otherwise main seems to have the changes from #17329

@dsplaisted
Copy link
Member

I had also added test coverage which seems to have gotten lost. Maybe you could try re-cherrypicking those commits?

mhutch and others added 3 commits May 13, 2021 14:11
Check dependencies in workload manifests (dotnet#16746)

* Implement workload manifest dependency validation

* Test workload manifest dependency validation

* Workload manifest version is now semver

* Update projects that link/reference WorkloadManifestReader
@sfoslund sfoslund force-pushed the WorkloadManifestVersions branch from c63fc35 to a5bda50 Compare May 13, 2021 21:14
@sfoslund
Copy link
Member Author

Maybe you could try re-cherrypicking those commits?

Sure, just pushed those instead of my changes

@sfoslund
Copy link
Member Author

StdOut:
MSBuild auto-detection: using msbuild version '16.10.0.18105' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\bin'.
StdErr:
C:\h\w\B44909B0\t\dotnetSdkTests\iu5e2p3p.enm\ItCanBuildPro---2831E99A\ItCanBuildProjectRestoredWithNuGet5_7\ItCanBuildProjectRestoredWithNuGet5_7.csproj : warning MSB4242: The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" failed to run. Missing or invalid manifest version
C:\h\w\B44909B0\p\d\sdk\6.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.props(14,3): warning MSB4242: The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" failed to run. Missing or invalid manifest version
C:\h\w\B44909B0\p\d\sdk\6.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.props(14,3): error : C:\h\w\B44909B0\p\d\sdk\6.0.100-ci\Sdks\Microsoft.NET.SDK.WorkloadAutoImportPropsLocator\Sdk not found. Check that a recent enough .NET SDK is installed and/or increase the version specified in global.json.
C:\h\w\B44909B0\p\d\sdk\6.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.props(14,38): error MSB4236: The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found. [C:\h\w\B44909B0\t\dotnetSdkTests\iu5e2p3p.enm\ItCanBuildPro---2831E99A\ItCanBuildProjectRestoredWithNuGet5_7\ItCanBuildProjectRestoredWithNuGet5_7.csproj]

@dsplaisted this is failing consistently, it looks like a workload resolver issue, do you have any ideas?

@dsplaisted
Copy link
Member

That test calls nuget.exe to restore, which ends up using the full Framework version of MSBuild. So it sounds like this is failing because the version of VS on the CI machine doesn't have the SDK resolver changes for the manifest version number schema change.

Probably if you change the test to set MSBuildEnableWorkloadResolver to false (currently it sets it to true) the test will start working. Otherwise we can disable the test until CI machines get updated.

@lewing
Copy link
Member

lewing commented May 15, 2021

A fix here needs to make it into preview5.

@sfoslund sfoslund enabled auto-merge May 17, 2021 16:10
@dsplaisted dsplaisted disabled auto-merge May 17, 2021 17:23
@dsplaisted
Copy link
Member

@sfoslund This needs to be retargeted to Preview 5, right? (I disabled auto-merge because of this.)

@sfoslund
Copy link
Member Author

@dsplaisted I was going to port it to preview 5 after it's in main

@sfoslund
Copy link
Member Author

Preview 5 PR: #17668

@sfoslund sfoslund merged commit 0d7e576 into dotnet:main May 17, 2021
@sfoslund sfoslund deleted the WorkloadManifestVersions branch May 17, 2021 17:28
ViktorHofer pushed a commit that referenced this pull request May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

workload install failing because of android manifest package version
5 participants