Skip to content

Release v4.10.0.0
Compare
Choose a tag to compare
@oleg-shilo oleg-shilo released this 29 Jul 12:11
· 20 commits to master since this release
v4.10.0.0
abd5521

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.9.0/; file=cs-script_4.9-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'.

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

  • -ng:csc is now using running csc.exe with the "magic" /shared parameter that keeps VBCSCompiler.exe running and improves the compilation performance dramatically.
  • -ng:csc is now routed to -ng:csc-inproc
  • WDBG:
    • Added disposing of abandoned user sessions
    • fixed problem with local methods in the call stack

CSScriptLib

  • CSScript.CodeDomEvaluator local build is now using running csc.exe with the "magic" /shared parameter that keeps VBCSCompiler.exe` running and improves the compilation performance dramatically (triggered by #423).
  • CodeDomEvaluator.CompileOnServer default value now is set to true.
  • CSScript.EvaluatorConfig.CompilerOptions now allows removing some of the default compiler options that you may find undesirable for whatever reason. This can be accomplished by specifying the option value with the !no prefix (e.g. !no/shared will remove /shared.
Assets 11
Loading