Predefined type 'System.Int32' is not defined or imported starting in v4.14.4

[Methuselah96]

My CS-Script test cases started failing with 4.14.4 when running them on Ubuntu. Here is a repo that demonstrates that the following code regressed in 4.14.4:

using CSScriptLib;

namespace TestCase;

public class Point
{
    public int X { get; set; }
    public int Y { get; set; }
}

[TestFixture]
public class DynamicEvaluationTests
{
    [Test]
    public void TestCSScript()
    {
        dynamic script = CSScript.Evaluator.LoadCode(
            @"using TestCase;
             public class Script
             {
                 public Point CreatePoint(int x, int y)
                 {
                     return new Point { X = x, Y = y };
                 }
             }"
        );
        var result = script.CreatePoint(1, 2);
        Assert.That(result.X, Is.EqualTo(1));
        Assert.That(result.Y, Is.EqualTo(2));
    }
}

Note that strangely this works on Windows, but not Ubuntu.

[oleg-shilo]

Noted. Thank you for repotting.
The investigation is in-progress

[oleg-shilo]

I do not have the environment for testing it right now, so may I ask you to do a little experiment?
Can you please repeat your test but with the environment variable set:

Environment.SetEnvironmentVariable("css_cli_roslyn_legacy_algorithm", "true");
dynamic script = CSScript.Evaluator.LoadCode(...

UPDATE: I have already tested it. Don't worry.

[oleg-shilo]

The problem is caused by System.Private.CoreLib bot being referenced automatically. While I am looking for the cause, you can temporarily address your problem with this workaround - add explicit ref:

dynamic script = CSScript.Evaluator
                         .ReferenceAssemblyOf<Point>() // important!
                         .ReferenceAssemblyOf<Int32>() // System.Private.CoreLib.dll
                         .LoadCode(code);

[frank-thole]

It seems we are seeing the same. With 4.14.4 and higher we now needs usings for many default types that previously just "worked". We are on Windows.

[oleg-shilo]

Yep, the problem is caused by the accidentally win-specific framework assemblies detection algorithm (fixed with 1e21659). This algorithm was reworked in the latest release, and a mistake was made. In result, the framework assemblies are not referenced automatically. Thus, the impact is wider than the CoreLib.dll.

While the workaround is to reference all assemblies at once with Evaluator.ReferenceDomainAssemblies(), I will publish the hotfix release right away.

Stay tuned.

[oleg-shilo]

Done.
You can update the package now:

dotnet add package CS-Script --version 4.14.6-Pre

If it works as expected, I will republish it as a proper release right away. Just did not want to do it without your feedback on teh fix.

[Methuselah96]

That seems to fix it, thanks!

[frank-thole]

Perhaps it resolves it on Linux. But it seems this issue is also on Windows.
Using our scripts, it works on our end with 4.14.3. When we upgrade to 4.14.6:

Or is this expected with the Roslyn changes? --> Doesn't seem to be the case, because 4.14.3 with Globals.DefaultRoslynCompilationToScript = false; also works.
Once upgrading to 4.14.4 (or newer), the issue in the screenshot happens.

[frank-thole]

I think it has to do with these changes? #450.