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
dotnet/coreclr#5144 unblocks us moving forward here, as soon as we can update the packages.
While InitializeDefaultContext was removed, thus spawning #1019, Dongbo Wang (@daxian-dbw) and I believe we can continue with PowerShell's assembly intercept method by creating a custom ALC in the powershell shim project, using that to load ConsoleHost, from which all all assemblies will be loaded. Since the rest of PowerShell's assembiles will be loaded from with that particular ALC, the loading will be intercepted, and .NET Core's changes will allow us to do this regardless of the assemblies being in the TPA (and without having to use the Resolving event).
Activity
andyleejordan commentedon Jun 21, 2016
dotnet/coreclr#5144 unblocks us moving forward here, as soon as we can update the packages.
While
InitializeDefaultContextwas removed, thus spawning #1019, Dongbo Wang (@daxian-dbw) and I believe we can continue with PowerShell's assembly intercept method by creating a custom ALC in thepowershellshim project, using that to loadConsoleHost, from which all all assemblies will be loaded. Since the rest of PowerShell's assembiles will be loaded from with that particular ALC, the loading will be intercepted, and .NET Core's changes will allow us to do this regardless of the assemblies being in the TPA (and without having to use theResolvingevent).