Skip to content

Release v4.8.9.0
Compare
Choose a tag to compare
@oleg-shilo oleg-shilo released this 16 Nov 00:07
· 116 commits to master since this release
v4.8.9.0
b03fa51
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.9.0/; file=cs-script_4.8-9.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:

cscs -self-alias

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 (combined 4.8.8.0-4.8.9.0)

CLI

v4.8.9.0

  • Updated NuGet support for .NET 8.0 packages
  • Added support for building css alias on Windows (to be used with WinGet distro)
    cscs -self-alias

v4.8.8.0

  • 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 project file for -ng:dotnet always targeting .NET 7

CSScriptLib

  • no changes
Assets 10
Loading