-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
MSBuild inconsistent file path to the same Task assembly load casing cast error #5080
Comments
The task in question here uses This retrieves an object from an ALC loaded through one path ( |
@rainersigwald So do you know what we need to do to fix this? Do keys for task objects need to now be aware of the ALC? |
There's an easy fix here for task objects used within a single assembly: normalize the path to that assembly. There's still a conceivable hole if the register/retrieve goes across assemblies (#5084), but I don't know if that actually happens. Since it might I think we should build an escape hatch back to legacy one-ALC behavior (#5086). |
Fixes dotnet#5080 by normalizing plugin assembly paths before deduplicating loads based on those paths. Does not fix the cross-assembly register/retrieve object problem dotnet#5084.
Fixes dotnet#5080 by normalizing plugin assembly paths before deduplicating loads based on those paths. Does not fix the cross-assembly register/retrieve object problem dotnet#5084.
Fixes dotnet#5080 by normalizing plugin assembly paths before deduplicating loads based on those paths. Does not fix the cross-assembly register/retrieve object problem dotnet#5084.
For posterity, this reproed at the commit here: dotnet/cli@cd47882 (thanks @sfoslund!) |
Steps to reproduce
Failed to build https://github.com/dotnet-maestro-bot/cli/tree/merge/release/3.1.1xx-to-release/3.1.2xx due to error:
The same assembly with different path is loaded
It is caused by path in https://github.com/microsoft/msbuild/blob/86d9494e446de002ea6a4f08d6fbd111b1041059/src/Shared/CoreCLRAssemblyLoader.cs#L32 is not normalized.
The text was updated successfully, but these errors were encountered: