Release v4.7.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.7.1.0/; file=cs-script_4.7-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 distrio 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 #327: CS-Script file with async calls suddenly terminates
• Added -install (-uninstall) command to set CSSCRIPT_ROOT environment variable.
• Added -kill command to stop all CS-Script servers (if any).

CSScriptLib

• <no changes>

Release v4.7.0.0

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.7.0.0/; file=cs-script_4.7-0.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 (choco)

choco install cs-script

.NET Tool (Any OS)

dotnet tool install --global cs-script.cli

You will need to add $HOME/.dotnet/tools folder to the system PATH.

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 distrio 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 #327: CS-Script file with async calls suddenly terminates
• Implemented new NuGet support (https://github.com/oleg-shilo/cs-script/wiki/NuGet-Support)
  • Issue #326: Types from .NET 7 NuGet package are not found
  • Issue #328: Using CS-Script inside a GitLab CI/CD Docker Runner
• Updated Linux distro with css executable replaced with Linux alias functionality.
• CS-Script CLI is published on nuget.org as a .NET tool cs-script.cli.

CSScriptLib

• <no changes>

Release v4.6.5.2

#Release Candidate 2

---

Changes

CLI

• Issue #327: CS-Script file with async calls suddenly terminates

• Implemented new NuGet support (https://github.com/oleg-shilo/cs-script/wiki/NuGet-Support)

  • Issue #326: Types from .NET 7 NuGet package are not found
  • Issue #328: Using CS-Script inside a GitLab CI/CD Docker Runner

• Issue #327: CS-Script file with async calls suddenly terminates

• Updated Linux distro with css executable replaced with Linux alias functionality.

CSScriptLib

Release v4.6.5

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.6.5.0/; file=cs-script_4.6-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

Windows (choco)

Currently pending Chocolaty approval...

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

The minimalistic manual distrio 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 #327: CS-Script file with async calls suddenly terminates
• Updated Linux distro with css executable replaced with Linux alias functionality.

CSScriptLib

• Added CodeDomEvaluator.CscTimeout to allow auto-termination of the csc.exe when it hangs. Triggered by #318

Release v4.6.4

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.6.4.0/; file=cs-script_4.6-4.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

Windows (choco)

Currently pending Chocolaty approval...

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

The minimalistic manual distrio 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

• CLI: Removed runtime dependency on *.CSharp.Scripting.CSharpScript.dll if Roslyn is not used as an engine.

CSScriptLib

• no changes

Release v4.6.3

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.6.3.0/; file=cs-script_4.6-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

Windows (choco)

Currently pending Chocolaty approval...

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

---

The primary feature of this release is WDBG - a web-based debugger.

Starting debugger:

css -wdbg script.cs

Read more

Changes

CLI

• WDBG: Fixed problem with invalid breakpoint info passing to client
• Added -new:webapi support

  css -new:webapi script.cs
  
  # or for minimalistic (no swagger) version
  css -new:webapi-min script.cs
  

CSScriptLib

no changes

Release v4.6.2

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.6.2.0/; file=cs-script_4.6-2.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

Windows (choco)

Currently pending Chocolaty approval...

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

---

The primary feature of this release is WDBG - a web-based debugger.

Starting debugger:

css -wdbg script.cs

Read more

Changes

CLI

• WDBG: implemented fully functional web-based debugger
• Issue #319: "Bad IL format" on self-contained linux-x64 builds if using namespace with same name as assembly
• Fixed false positive of OutOfDate detection. Caused by the imported files stored in the script file stamp without their full path

CSScriptLib

no changes

Full Changelog: v4.6.1.0...v4.6.2.0

Release v4.5.0.0

Deployment

Ubuntu (terminal)

repo=https://github.com/oleg-shilo/cs-script/releases/download/v4.5.0.0/; file=cs-script_4.5-0.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
Windows (choco)

Currently pending Chocolaty approval...

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

---

Due to the quick progression v4.4.9->v4.5.0 this document contains v4.4.9 changes too.

Changes

CLI

v4.5.0

• Rebuild for .NET7
• Improved CLI documentation (triggered by #314)
• Added an extra CLI //css_co help sample for enabling nullable reference types (#313)
• Improved responsiveness of the "build-type" scripting scenarios (e.g. css -check)

v4.4.9

• Enhancement #310: Add the possibility to use variables in css_include and css_import statements

CSScriptLib

v4.4.9

• It's possible to define a custom algorithm of how to expand script directives.

  Hosting code:

  CSScript.EvaluatorConfig.ExpandStatementAlgorithm += 
                  statement => statement.Replace("%secret_folder%", Config.PrivateFolder);

  Script code:

  //css_include %secret_folder%/inputdata.cs
  . . .

Release v4.4.9.0

• Enhancement #310: Add the possibility to use variables in css_include and css_import statements

It's possible to define a custom algorithm of how to expand script directives.

Hosting code:

  CSScript.EvaluatorConfig.ExpandStatementAlgorithm += 
                statement => statement.Replace("%secret_folder%", Config.PrivateFolder);

Script code:

  //css_include %secret_folder%/inputdata.cs
  . . .

Release v4.4.8.0

Deployment

Ubuntu (terminal)

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

Windows (choco)

choco install cs-script

Manual (Any OS)

Just unpack the corresponding 7z file and start using the script engine executable cscs.
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 package.

---

Changes

CLI

• Fixed the problem with possible double referencing GAC assemblies for CSC engine due to the nuget dependencies on GAC assemblies of the different versions.

CSScriptLib

• no changes