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.23.0/; file=cs-script_4.8-23.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
Note: this very release is not available on Chocolatey and WinGet but only on Nuget (.NET tool) as described above.
If you tr to install from Chocloaltey or WinGet, it will install the previous .NET 8.0 build of CS-Script
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
- #396 Some NuGet packages are not recognized and not referenced
- #397: How to succeed in using NuGet packages with native binaries (like e.g. SkiaSharp)
- I added a new command,
-list,
to print all currently running scripts. - Added support for nuget package native assets
- LegacyNugetSupport by defaults made false
- script compilation cache now stores probing dirs to allow recreation of PATH environment variable during the cached execution (e.g. to cover nuget native assets)
- Added support for
-self-install
command to set globalCSSCRIPT_ROOT
envar. - Updated
//css_nuget
syntax CLI documentation
CSScriptLib
- no changes