-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
System.Resources.Extensions fails to load due to missing binding redirect when transitively referenced (e.g. in test project) #50286
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I see. We should probably put this targets file into |
Tagging subscribers to this area: @tarekgh, @buyaa-n, @krwq Issue DetailsSteps to reproduce:
Upon inspection in both the real-world project and the attached repro, this is present in the main project's .config file but not in the test project's, even though the test project is transitively referencing System.Resources.Extensions: <dependentAssembly>
<assemblyIdentity name="System.Resources.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.0.0.0" />
</dependentAssembly> This workaround fixes the problem, but it should not be required to add this to projects that already transitively reference this package: <ItemGroup>
<!-- Workaround for https://github.com/dotnet/sdk/issues/16522 -->
<PackageReference Include="System.Resources.Extensions" Version="5.0.0" />
</ItemGroup>
|
Steps to reproduce:
dotnet test
Upon inspection in both the real-world project and the attached repro, this is present in the main project's .config file but not in the test project's, even though the test project is transitively referencing System.Resources.Extensions:
This workaround fixes the problem, but it should not be required to add this to projects that already transitively reference this package:
The text was updated successfully, but these errors were encountered: