@atifaziz Want to take a look at this? 😃

@atifaziz Want to take a look at this? 😃

Had a quick look and proposed a fix in PR #724 for the "#load directive with next expression start with string" problem.

2. using statement without parenthesis or a block on top level

I do believe this is not allowed in a script so not sure anything can be done about it. While not officially documented, see dotnet/roslyn#28588 where it says:

• test scripting (should disallow using-declaration, maybe some additional complications)

I try to transform my LINQPad queries to dotnet-script. In LINQPad 1, 2 work without problems.

I try to transform my LINQPad queries to dotnet-script. In LINQPad 1, 2 work without problems.

@i-mark LINQPad doesn't use C# scripting like this tool so it's not bound to the same restrictions. LINQPad turns your query/script into a whole C# program, somewhat like what I emulate in LINQPadless.

I try to transform my LINQPad queries to dotnet-script. In LINQPad 1, 2 work without problems.

@i-mark LINQPad doesn't use C# scripting like this tool so it's not bound to the same restrictions. LINQPad turns your query/script into a whole C# program, somewhat like what I emulate in LINQPadless.

Ok, thx.

I run it with c# scripting and this code throw (1,11): error CS1002

var options = ScriptOptions.Default
		.AddReferences(typeof(Console).Assembly)
		.AddImports("System")
		.AddImports("System.IO");

//var statement = "using (var ms = new System.IO.MemoryStream()) {};";
var statement = "using var ms = new System.IO.MemoryStream();";
await CSharpScript.RunAsync(statement);