-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add System.Reflection.PathAssemblyResolver support for 'retargetable' assemblies #730
Comments
@steveharter can you port fca6032 to release/3.1 and drive through servicing process? |
Moved to dotnet/runtime for centralized query. cc @ericstj, @nguerrera, @rladuca, @steveharter since notifications will have gotten lost. |
Picking this up, discussed in tactics and approved if it makes it in today. |
Per @mmitche dotnet/corefx#42768 (comment)
|
This was fixed in 3.1.2 with package System.Reflection.MetadataLoadContext\4.7.1. WPF is still working on picking up the fix in the SDK. |
https://github.com/dotnet/corefx/issues/40523#issue-484261911
This was fixed in .NET 5 - dotnet/corefx#40581. We did not take this change into .NET Core 3.1 since the evidence was not clear at that time that this would be a big problem.
Since the release of .NET Core 3.1, several WPF customers have reported that this is a blocking problem.
We would like this fix backported to .NET Core 3.1 as part of an upcoming servicing update.
/cc @ericstj, @nguerrera, @rladuca, @steveharter
The text was updated successfully, but these errors were encountered: