Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/oleg-shilo/cs-script/releases below:

Releases · oleg-shilo/cs-script · GitHub

Releases · oleg-shilo/cs-script

Note

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

• cs-script.win.v4.11.0.0.zip ✅(0/97) VirusTotal latest scan

Installing

• CLI tool: dotnet tool install --global cs-script.cli
• Hosted class library in .NET Project: create the project from the WixSharp Project template.

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).

Ubuntu (terminal)

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

Chocolatey (pending approval

WinGet (pending approval)

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>

• fixed problem with css -ls <kill-all|ka>
• Added support for pre-release packages //css_nuget -pre <package>
• WDBG:
  • Improved tracking of declaration scope
  • UX improvements
  • Inject dbg metadata is ported to pure Roslyn.
  • Detect debug metadata out of sync and report it (2)

• Added NativeAOT sample
• CodeDomEvaluator.CompileOnServer is made obsolete (with error)

Note

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

• cs-script.win.v4.10.1.0.zip ✅(0/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

All changes delivered by CS-Script v4.10.0 plus:

• WinDebugger usability changes
• Repackaged CSScriptLib as v4.10.0 had a packaging mistake.

v4.10.0 Changes

• -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

• 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.

Note

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

• cs-script.win.v4.10.0.0.zip ✅(0/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• -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

• 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.

Note

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

• cs-script.win.v4.9.9.0.zip ✅(0/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• added cscs.exe to the cs-script.cli .NET Tool package (triggered by #423)
• added option for css -cache <script> command to print the cache location for a given script
• WDBG:
  • Implemented Call Stack panel
  • implemented "New Script" functionality
  • on switch doc restore caret and scroll position
  • show "is modified" mark in the project tree
  • implemented dbg-step-out
  • mult-file support
  • code formatting and line breaks normalization
  • autocompletlion and tooltips are styled with themes

• no changes

Note

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

• cs-script.win.v4.9.8.0.zip ✅(1/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

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.

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

v4.9.7

• #416: CompileInfo parameter for CompileMethod()

Note

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

• cs-script.win.v4.9.7.0.zip ✅(1/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• 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

• #416: CompileInfo parameter for CompileMethod()

Note

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

• cs-script.win.v4.9.6.0.zip ✅(0/97) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

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

<no changes>

Note

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

• cs-script.win.v4.9.5.0.zip ✅(0/96) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• 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

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

Note

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

• cs-script.win.v4.9.4.0.zip ✅(0/96) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• #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

• no changes

Note

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

• cs-script.win.v4.9.3.0.zip ✅(0/96) VirusTotal latest scan

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).

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.

Chocolatey (pending approval

WinGet (pending approval)

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>

• 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

• no changes

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

• no changes

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4