Change version check from != to < to allow loading newer assembly versions when older versions are requested. #12909
+86
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
Change version check from != to < to allow loading newer assembly versions when older versions are requested. #12370
Context
MSBuildLoadContext was using exact version matching (!=) when loading assemblies, preventing version roll-forward. This caused tasks to fail when requesting an older assembly version even though a newer compatible version was available.
Changes Made
!=to<(line 86)MSBuildLoadContext_AcceptsNewerAssemblyVersionsin TaskBuilder_Tests.csValidateAssemblyVersionRollForwardin AssemblyLoadContextTestTasks.csTesting
Notes
This change allows MSBuildLoadContext to accept any assembly version >= requested version, matching standard .NET assembly loading behavior.