Repository navigation
Retire explicit paths in clr.AddReference #1514
Description
We had plenty of issues with explicit path usage (just stumbled over #1011 which I'll close in favour of this one) in clr.AddReference calls. I propose that we only allow names instead of paths in the future as this is much more "compatible" with the proposed way of using .NET Core (runtimeconfig from a published folder).
Activity
lostmsu commented on Aug 9, 2021
I am not sure what the problem is exactly. In .NET (including Core) Assembly.LoadFile works fine. The only caveat is that upon calling it all dependencies must already be either loaded, or accessible in PATH (or its *nix equivalent).
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…
fixed FileLoadException when trying to do clr.AddReference('/full/lib…