Skip to content

Releases: oleg-shilo/cs-script

Release v4.9.8.0

09 Jun 09:25
@oleg-shilo oleg-shilo
v4.9.8.0
2bd68b0
Compare
Choose a tag to compare
Release v4.9.8.0 Latest
Latest

Note

Windows Defender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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 release is identical to v4.9.7 functionality-wise. It only delivers a minor change to the supplementary tool WDBG (web debugger for cs-script) but not to the engine itself.

CLI

v4.9.8

  • WDBG - web application changed to allow self-discovery of cscs.dll.

v4.9.7

  • Stop killing its own process on css -lists kill *
  • Bumped version: Microsoft.CodeAnalysis.CSharp.Scripting v4.14.0
  • New WDBG environment
  • WDBG - Addressed multiple parsing problems when preparing the script for execution

CSScriptLib

v4.9.7

  • #416: CompileInfo parameter for CompileMethod()
Assets 10
Loading

Release v4.9.7.0

08 Jun 11:20
@oleg-shilo oleg-shilo
v4.9.7.0
2bd68b0
Compare
Choose a tag to compare
Release v4.9.7.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Stop killing its own process on css -lists kill *
  • Bumped version: Microsoft.CodeAnalysis.CSharp.Scripting v4.14.0
  • New WDBG environment
  • WDBG - Addressed multiple parsing problems when preparing the script for execution

CSScriptLib

  • #416: CompileInfo parameter for CompileMethod()
Loading

Release v4.9.6.0

27 Apr 01:57
@oleg-shilo oleg-shilo
v4.9.6.0
d8d3c7d
Compare
Choose a tag to compare
Release v4.9.6.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

#414: Implement assembly probing for external script execution (e.g. x86)

CSScriptLib

<no changes>

Loading

Release v4.9.5.0

16 Apr 13:00
@oleg-shilo oleg-shilo
v4.9.5.0
982ccaf
Compare
Choose a tag to compare
Release v4.9.5.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

Deployment (installation Instructions)

Deployment

Any OS

NOTE
Since this release delivers only extended command -unlock script changes this release was only published on nuget.org as a .NET Tool.

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Added support for resolving nuget assemblies to the RID (runtime) specific assemblies
  • Added advising user to restart build server if previously detected csc.dll cannot be found.
  • Fixed problem with running scripts not registering themselves in %userprofile%\AppData\Local\cs-script\p-list
  • #409 CS-Script 4.8.21 requires .NET 9 runtime

CSScriptLib

  • #409 CS-Script 4.8.21 requires .NET 9 runtime
Loading

Release v4.9.4.0

10 Mar 10:38
@oleg-shilo oleg-shilo
v4.9.4.0
423bea6
Compare
Choose a tag to compare
Release v4.9.4.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

Deployment (installation Instructions)

Deployment

Any OS

NOTE
Since this release delivers only extended command -unlock script changes this release was only published on nuget.org as a .NET Tool.

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • #406: Custom DLL (CommandGathering.dll) Fails Compile-Time Namespace Resolution with //css_ref
  • Improved css -cmd UX when generating custom commands descriptions.
  • Updated custom commands -pkill to allow killing the process by PID.
  • Added custom commands:
    • -runas
    • -which
    • -who

CSScriptLib

  • no changes
Loading

Release v4.9.3.0

24 Feb 11:17
@oleg-shilo oleg-shilo
v4.9.3.0
5a31846
Compare
Choose a tag to compare
Release v4.9.3.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

Deployment (installation Instructions)

Deployment

Any OS

NOTE
Since this release delivers only extended command -unlock script changes this release was only published on nuget.org as a .NET Tool.

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Added new custom commands:
    • css -pkill <process name pattern>: terminates the process based on name.
    • css -update: updates already installed CS-Script (if detected)
    • css -edit <script|custom command>: opens the script in the default editor
  • Improved dev experience for css -new:cmd <name>:
    • Now name can include dash as a prefix.
    • Handle the case when during command creation with -new:cmd the file name is a command that starts with two dashes (e.g. -ver vs --version)handle

CSScriptLib

  • no changes

Changes

CLI

  • Fixed css -update problem when trying to update itself locked by the current process
  • Improved CLi help for custom commands

CSScriptLib

  • no changes
Loading

Release v4.9.2.0

23 Feb 08:35
@oleg-shilo oleg-shilo
v4.9.2.0
fe4c19f
Compare
Choose a tag to compare
Release v4.9.2.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

Deployment (installation Instructions)

Deployment

Any OS

NOTE
Since this release delivers only extended command -unlock script changes this release was only published on nuget.org as a .NET Tool.

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Added new custom commands:
    • css -pkill <process name pattern>: terminates the process based on name.
    • css -update: updates already installed CS-Script (if detected)
    • css -edit <script|custom command>: opens the script in the default editor
  • Improved dev experience for css -new:cmd <name>:
    • Now name can include dash as a prefix.
    • Handle the case when during command creation with -new:cmd the file name is a command that starts with two dashes (e.g. -ver vs --version)handle

CSScriptLib

  • no changes

Changes

CLI

  • Added new custom commands:
    • css -pkill <process name pattern>: terminates the process based on name.
    • css -update: updates already installed CS-Script (if detected)
    • css -edit <script|custom command>: opens the script in the default editor
  • Improved dev experience for css -new:cmd <name>:
    • Now name can include dash as a prefix.
    • Handle the case when during command creation with -new:cmd the file name is a command that starts with two dashes (e.g. -ver vs --version)handle

CSScriptLib

  • no changes
Loading

Release v4.9.1

09 Feb 05:56
@oleg-shilo oleg-shilo
v4.9.1.0
642d43d
Compare
Choose a tag to compare
Release v4.9.1

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

Deployment (installation Instructions)

Deployment

Any OS

NOTE
Since this release delivers only extended command -unlock script changes this release was only published on nuget.org as a .NET Tool.

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Added support for versioning of custom commands during css -new:cmd ...
  • Added custom command -unlock

CSScriptLib

  • no changes
Loading

Release v4.9.0.0

02 Feb 05:46
@oleg-shilo oleg-shilo
v4.9.0.0
cbab3f4
Compare
Choose a tag to compare
Release v4.9.0.0

Note

WindowsDefender often marks zip files as infected for no reason. Use VirisTotal reports to ensure the safety of any downloaded distributable:

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, if you want to use this feature, it needs to be done manually (sudo css -server:add).

Linux

Ubuntu (terminal)

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

Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.

Windows

Chocolatey (pending approval

choco install cs-script

WinGet (pending approval)

winget install cs-script

Manual (Any OS)

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

When using on Windows, you can build an alias(shim) exe css.exe for an easy launch of the script engine process: cscs -self-alias.
The same shim is created if you are installing the CS-Script as a choco package.

Barebone distribution

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

  • Added support for versioning of custom commands
  • Fixed potential infinite loop on SocketError in the build server

CSScriptLib

  • no changes
Loading

Release v4.8.27.0

12 Jan 07:42
@oleg-shilo oleg-shilo
v4.8.27.0
1945af6
Compare
Choose a tag to compare
Release v4.8.27.0

Changes

CLI

  • no changes (use Release v4.8.26.0)

CSScriptLib

  • Restored ability to host on .NET Framework by refactoring and avoiding JIT trying to load incompatible Roslyn types when hosting on .NET Framework
Loading