You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Reflection patterns can not resolve assemblies outside of the reference closure #943
When a supported reflection pattern references an assembly that is part of the linker input set, but not in the reference closure of any roots (and thus not loaded into the LinkContext assemblies by LoadReferencesStep or any other step that comes before MarkStep), the pattern will fail to resolve. Since simple reflection patterns are often used for activation without a build-time dependency, this seems like something worth supporting. See dotnet/sdk#4017 for the original issue with a repro.
#843 is a similar issue where PreserveDependency doesn't cause xml roots from the referenced assembly to be processed.
Activity
Enable recursive processing of dynamic assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
Enable processing of dynamically referenced assemblies
marek-safar commentedon Feb 26, 2021
I believe this should be fixed. @sbomer could you please undo the runtime change so we can fully verify this and close ?
sbomer commentedon Mar 12, 2021
Fixed by #1666, runtime workarounds removed in dotnet/runtime#49523.