[release/9.0-staging] Move generation of SuggestedBindingRedirects.targets to inner build #112487
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
These targets depend on the AssemblyVersion of the library which is specific to the inner-build of the library. Generate them in the inner-build.
….Extensions.csproj
|
Tagging subscribers to this area: @dotnet/area-system-resources |
ViktorHofer
approved these changes
Feb 12, 2025
rbhanda
added
Servicing-approved
|
Failures are #112312 which was just fixed. |
|
/ba-g failures are all known. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #112379 to release/9.0-staging
Fixes #111892
/cc @ericstj
Customer Impact
.NETFramework project using the latest System.Resources.Extensions package fails to load resources with
FileLoadException.Regression
9.0.1 - this is the first time we've serviced this package. The package didn't account for the serviced assembly version correctly.
Testing
Build / package / inspect redirects. Manually test consuming package in .NETFramework project.
Automated tests here are difficult with current infrastructure as we don't consume the built packages, nor rely on auto-generated bindingRedirects in the same way a customer project does.
Risk
Low - updating target in a single project that only impacts that library's generation of a targets file. If it builds its good.
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging, notrelease/X.0.Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.