Oleksiy Gapotchenko

Can I work on this task? The plan: 1. Change `AppDomain` usages to functionality provided by `AssemblyLoadContext` 2. Allow passing an optional `AssemblyLoadContext` instance in higher-level options such as `ExecuteScriptCommandOptions`....

I was able to come up with a successful prototype implementation. Now working on a formal pull request.

It seems that there is an already loaded assembly with the same name `Microsoft.CodeAnalysis` but with different version. The current implementation does not use `AssemblyLoadContext` functionality of .NET, so the...

A naïve approach trying to reproduce the issue works as expected. test.csx: ```csharp using System.IO.Compression; var ms = new MemoryStream(); var cs = new DeflateStream(ms, CompressionMode.Compress); var bw = new...

>It will return null. Should this be the ScriptAssemblyLoadContext It should not return `null`. Are you trying this in interactive mode?

> var loadContext = AssemblyLoadContext.CurrentContextualReflectionContext; Was able to reproduce it with `dotnet-script` 1.2.0 global tool installed, but not with locally built binaries. Upon closer inspection, it turned out that `%USERPROFILE%\.dotnet\tools\.store\dotnet-script\1.2.0\dotnet-script\1.2.0\tools\net5.0\any\Dotnet.Script.Core.dll`...

>!NETSTANDARD2_0 That line does not need `NETCOREAPP3_0_OR_GREATER` condition anymore as we dropped `netcoreapp2.1`. Not a problem, as it will be covered in a test after implementation of opt-in option. It...

Please be sure to save the input file in UTF-8 encoding. The issue should be solved.

Funny like this fairly frequently desired feature gets ignored for years. I understand that such a convenience clearly goes against paid/pro plans. A possible solution: include it in a paid...

This behavior is spotted on Kestrel. (I've just added that info to the original message)