Cannot use CSharpScript API with PublishSingleSingle option

[CyberSinh]

Hi,

I use the following code to run C# scripts in my software. Everything is fine under .NET 5.0 when I publish the software without PublishSingleSingle option.

ScriptOptions options = ScriptOptions.Default
   .WithMetadataResolver(ScriptMetadataResolver.Default.WithSearchPaths(new[] { RuntimeEnvironment.GetRuntimeDirectory(), AppInfo.StartupFolder }))
   .WithSourceResolver(new SourceFileResolver(ImmutableArray<string>.Empty, AppInfo.ScriptsFolder))
   .AddReferences(Assembly.GetExecutingAssembly()); // Assembly.Location returns "" with PublishSingleFile option, but using Environment.GetCommandLineArgs()[0] instead Assembly.GetExecutingAssembly() doesn't work too
   
Script script = CSharpScript.Create(code, options, typeof(GlobalVariables));
//Script script = CSharpScript.Create(code, null, null); // using CSharpScript with default parameter doesn't work too
script.Compile();

But when I publish my software with the PublishSingleFile option, the code doesn't work anymore and I get the error:
"can't create a metadata reference to an assembly without location".

Is there is a way to reference my main assembly and/or .NET 5.0 system assemblies embedded in the main executable?
Is there any code sample to use the CSharpScript API when PublishSingleFile is enabled?

Thanks for your help.

[jinujoseph]

cc @tmat

[andersstorhaug]

Simple reproduction, with .NET 5 and PublishSingleFile set to true.

await CSharpScript.EvaluateAsync(@"""Hello World!""");

The issue seems to be from Script.GetReferencesForCompilation:

var corLib = MetadataReference.CreateFromAssemblyInternal(typeof(object).GetTypeInfo().Assembly);

Maybe this workaround could be helpful for single-file publish?

public static MetadataReference GetRawMetadataReference(this Type type)
{
    unsafe
    {
        return type.Assembly.TryGetRawMetadata(out var blob, out var length)
            ? AssemblyMetadata
                .Create(ModuleMetadata.CreateFromMetadata((IntPtr) blob, length))
                .GetReference()
            : throw new InvalidOperationException($"Could not get raw metadata for type {type}");
    }
}

[BlackOfWorld]

Same issue here, don't know how to fix it 😿

[BlackOfWorld]

@andersstorhaug have you found any reliable fix for this issue?

[andersstorhaug]

@BlackOfWorld I haven't found a workaround for this yet, though, this StackOverflow post may be of some use.

[BlackOfWorld]

I think it could be solved by memory patching IL code, but I find it very hacky workaround.

[andersstorhaug]

Here's an example that I was able to get working by effectively (and naively) reproducing the CSharpScript API with the aforementioned mscorlib MetadataReference workaround.

[Squirrelies]

This just bit me in the tail feather today using .NET 6.0 RTM (6.0.100). Any update on whether this will be addressed in a future release? The workaround did not work for me when adding the assemblies to ScriptOption.Default.AddReferences() and supplying that ScriptOptions instance to CSharpScript.EvaluateAsync() in Single-File Publish mode.