fix: Align Microsoft.Extensions package versions in ExperimentFramework.csproj #51
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.
Description
Fixed version inconsistency where concrete Microsoft.Extensions packages were pinned to 9.0.11 while their abstractions were using variable versioning (10.0.1 for net10.0). This caused CI build failures due to package version mismatches across multi-targeted frameworks.
Type of Change
Related Issues
N/A - CI build failure correction
Changes Made
Microsoft.Extensions.Configurationto use$(MicrosoftExtensionsVersion)instead of hardcoded "9.0.11"Microsoft.Extensions.DependencyInjectionto use$(MicrosoftExtensionsVersion)instead of hardcoded "9.0.11"Testing
Test Configuration
Checklist
Screenshots (if applicable)
N/A
Additional Context
The fix ensures version consistency across all Microsoft.Extensions packages for all target frameworks (net8.0, net9.0, net10.0), preventing runtime binding conflicts and CI build failures.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.