cs-script: vecākas versijas un visa vēsture

- IFixed problem with .build directory being cleared/removed before another process using it finishes the work. - Fixed problem with false positive in the IsOutdated test for script caching. Was caused by the inclusion of the current dir in the evaluation.

- Improvements in the `-csproj` and `-vs` command implementation. - Added handling Web projects. - Improved invalid directory handling in the command handlers.

Added -proj:out to create a Visual Studio project file for building the exe file from the script." #467: SelfContained does not work anymore since version 4.14.4

Added multi-file and symbol support to Roslyn build pipeline (`-ng:roslyn`)

Improved script assembly location tracking. Now, even if the script assembly is loaded not from a file but from memory, the location can still be resolved in the script via CS-Script's own extension method Assembly.Location()

- #432: "Restoring packages..." hangs

- Added compiler `NET10_0_OR_GREATER` and `NET10` for .NET10 scripts.

- Added public ConsoleExtensions

```c#

Console.Print("Running on .NET 10 or greater", DarkGreen);

Console.Print("Hello");

var name = Console.Prompt("Enter your name: ", DarkYellow);

```

- CS-Script ported to .NET 10

- Added '-l' option for auto-selecting the latest available .NET Runtime with the call: `css -self-rt -l`

- Added support for .NET 10 file-based execution directives: `#:package` and `#r`.

- Changed the search dir priorities to low local overwrite of the distributed included scrips (libs): `%CSSCRIPT_INC%` is now higher than "%CSSCRIPT_ROOT%/lib`

- In the `css.exe` status print out is now saying `<not set>` instead of `<not integrated>` for the InstallationDir field.

It's not really about the integration but setting the CSSCRIPT_ROOT envar.

- Updated `ProjectBuilder.GenerateProjectFor` to include the script engine assembly and global includes (e.g. `global-usings`)

- Updating current directory via -l switch is disabled for all custom command scripts.
- Added public extension methods
- Reset dotnet-engine project template on the change of the target framework (set via `-self-rt`)
- Added a small automation library `shell.cs` to the distribution
- added `-scrumble` custom command
- added `shell.cs` lib-script

- Added `-self-rt` custom command for setting the script engine runtime version

- 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

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

Changes
CLI
#414: Implement assembly probing for external script execution (e.g. x86)
CSScriptLib
- 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.4.0.zip ✅(0/96) VirusTotal latest scan
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

- 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

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.1.0.zip ✅(0/96) VirusTotal latest scan
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