Open twsouthwick opened 3 years ago
MSBuild itself has some assumptions about running in the default ALC. I don't think we had a bug for that so I filed https://github.com/dotnet/msbuild/issues/6794.
Until that is fixed, I'm not sure if there's value in changing Locator's behavior, but as soon as it's possible/supported to load MSBuild in an ALC Locator should definitely support/encourage it as well.
This also gets my vote, I have requirements to maintain the lifetime of and unload msbuild from my process when done with it.
Currently, the MSBuild assemblies are loaded into the default AssemblyLoadContext. However, I'm interested in being able to load it into a seprate one so I can manage its lifetime separately from the rest of the app.
There are two ways I see this can be added:
AssemblyLoadContext.Default
to.CurrentContextualReflectionContext
(which will require adding a .NET Core 3.1+ target)RegisterMSBuild{xxx}(...)
that takes anAssemblyLoadContext
Problems with this:
AssemblyLoadContext
and currently wouldn't understand an assembly load context being unloadedThe first problem is surmountable by changing how it's tracked that MSBuild is loaded. The second issue is something I don't have an answer for.