Release v4.8.8.0

Deployment (installation Instructions)

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note:

• before upgrading the already installed tool you may need to ensure the script engine is not running. You can do it with a simple command css -kill.
• you may prefer to enable an optional build server (see css -server ?) to boost script compilation performance. On Windows it's done automatically on the very first execution but on Linux it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.8.0/; file=cs-script_4.8-8.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Note, if you like using the alias css, you will need to create it manually as WinGet does not support aliases for portable packages. Execute the following line in CMD or PS terminal:

cmd /K "cd %userprofile%\AppData\Local\Microsoft\WinGet\Packages\oleg-shilo.cs-script__DefaultSource & mklink /H css.exe cscs.exe"

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:

Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

Changes

CLI

• Rebuilt for .NET 8.0
• First WinGet release
• Chocolatey package changed to address shim ambiguity with css.exe. Now it is a true shim generated by choco script.
• There is no custom-build css.exe shim in the Chocolatey package. Instead, the css.exe native chocolatey shim to cscs.exe is created at runtime. The same way as for DotNet-tool and WinGet packages.
• Fixed problem with the default proj fle for -ng:dotnet always targeting .NET 7

CSScriptLib

• no changes

Release v4.8.7.0

Deployment (installation Instructions)

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note:

• before upgrading the already installed tool you may need to ensure the script engine is not running. You can do it with a simple command css -kill.
• you may prefer to enable an optional build server (see css -server ?) to boost script compilation performance. On Windows it's done automatically on the very first execution but on Linux it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.7.0/; file=cs-script_4.8-7.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocoloatey

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:

Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

Changes

CLI

• Fixed accidental ignoring of CLI arguments: -v, -ver, -version
• Improved CLI help formatting
• Improved build script

CSScriptLib

• no changes

Release v4.8.7.1

Deployment (installation Instructions)

Deployment

Windows

Chocoloatey

choco install cs-script

Changes

There are no CS-Script functional changes.
This is a specific distro-oriented release that allows the introduction of WinGet support as well as aligning Chocolatep package architecture with the rest of the package managers:

• There is no custom-build css.exe shim in the Chocolatey package. Instead the css.exe native chocolatey shim to cscs.exe is created at runtime. The same way as for DotNet-tool and WinGet packages.

NOTE, THE PACKAGES ARE STILL UNDER CONSTRUCTION

CLI

• no changes

CSScriptLib

• no changes

Release v4.8.6.0

Release v4.8.6.0

Deployment (installation Instructions)

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note:

• before upgrading the already installed tool you may need to ensure the script engine is not running. You can do it with a simple command css -kill.
• you may prefer to enable an optional build server (see css -server ?) to boost script compilation performance. On Windows it's done automatically on the very first execution but on Linux it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.6.0/; file=cs-script_4.8-6.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocoloatey

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:

Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

Changes

CLI

The changes impact only script execution on Linux.

• Issue #345: cs-script 4.8.5 does not see cache directory on Linux
• Issue #346: cs-script 4.8.5 doesn't show information about server on Linux

CSScriptLib

• no changes

Release v4.8.5

Release v4.8.3.0

Deployment (installation Instructions)

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note, that during the tool upgrade you may need to ensure the script engine is not running. You can do it with a simple command css -kill.

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.5.0/; file=cs-script_4.8-5.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocoloatey

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:

Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

Changes

CLI

• Issue #344: Support .csx file extension?

CSScriptLib

• no changes

Pre-Release v4.8.4.0

Changes

CLI

• no changes

CSScriptLib

• Issue #343: Publish to single file gives an empty Assembly.Location which crashes Roslyn Evaluator
  Added support for single-file publishing with runtime dependency

Release v4.8.3.0

Release v4.8.3.0

Deployment (installation Instructions)

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note, during the tool upgrade you may need to ensure the script engine is not running. You can do it with a simple command css -kill.

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.3.0/; file=cs-script_4.8-3.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocoloatey

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:
Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

Changes

This is the first release that supports scripting from applications published with PublishSingleSingle (Roslyn defect dotnet/roslyn#50719). Thanks to workaround described here CS-Script provides a transparent way for supporting this deployment scenario. Thius the following code will work just fine regardless how you built/published your application:

var calc = CSScript.Evaluator
                   .Eval(@"using System;
                           public class Script
                           {
                               public int Sum(int a, int b)
                               {
                                   return a+b;
                               }
                           }
                           return new Script();");

int sum = calc.Sum(1, 2);
Console.WriteLine(sum);

The complete sample can be found here.

CLI

• Issue #336 (further optimization)

CSScriptLib

• Issue #343: Publish to single file gives an empty Assembly.Location which crashes Roslyn Evaluator
• Added support for single-file published host applications
• Added new me evaluator method for simple expression evaluation: int div = CSScript.Evaluator.Eval("3+8");

Release v4.8.2.0

Changes

CLI

• Issue #336 (further optimization)

CSScriptLib

• no changes

Release v4.8.1.0

Deployment

Any OS

Install as .NET Tool

dotnet tool install --global cs-script.cli

After that, you can invoke the script engine as css.
You may need to add the folder of css to the system PATH, unless .NET SDK setup does it.
It can be one of these depending on your OS:

• %USERPROFILE%\. dotnet\tools
• ~/.dotnet/tools
• $HOME/.dotnet/tools

Note, during the tool upgrade you may need to ensure the script engine is not running. You can do it with a simple command css -kill.

Linux

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.8.1.0/; file=cs-script_4.8-1.deb; rm $file; wget $repo$file; sudo dpkg -i $file

Depending on the user context you may need to add permissions to the CS-Script temp dir sudo chmod -R 777 /tmp

You can also create a convenient alias (cs-script_x.x-x.deb package does it automatically):

alias css='dotnet /usr/local/bin/cs-script/cscs.dll'+

After that, you can invoke CS-Script engine from anywhere by just typing 'css'.

Windows

Chocoloatey

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.

On Windows, if you prefer you can build a shim exe css for an easy launch of the script engine process:

dotnet cscs -self-exe

The same shim/symbolic link is created if you are installing the CS-Script as a choco package.

The minimalistic manual distro on the target machine with .NET SDK installed is just a set of the script engine files:
Linux

cscs.dll
cscs.runtimeconfig.json

Running: dotnet ./cscs.dll <script>

You can also create an alias for convenient access:

echo "alias css='dotnet /usr/local/bin/cs-script/cscs.dll'" >> ~/.bashrc
source ~/.bashrc

And then you can run scripts with a simple: css <script>

Windows

cscs.exe
cscs.dll
cscs.runtimeconfig.json

Running: cscs.exe <script>

---

Changes

CLI

• Issue #336: Huge script startup delay with v4.7.2.0 compared to v4.2.0.0

CSScriptLib

• Added CSScriptLib.ScriptParser.ImportedSourceFiles to allow access to the dependency script's raw files
• Added option to set assembly name when compiling script with Roslyn; Triggered by #337

Release 4.8.0.0

Changes

CLI

• Issue #334: Concurrent compilation
• Improved CLI-help content.

CSScriptLib

• Issue #335: CompileAssemblyFromFile with CompileInfo