Downloads:

884

Downloads of v 2.0.0.0:

73

Last Update:

21 Feb 2021

Package Maintainer(s):

Software Author(s):

  • Oleg Shilo

Tags:

cs-script C# script dynamic hosting

CS-Script.Core

2.0.0.0 | Updated: 21 Feb 2021

Downloads:

884

Downloads of v 2.0.0.0:

73

Maintainer(s):

Software Author(s):

  • Oleg Shilo

CS-Script.Core 2.0.0.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install CS-Script.Core, run the following command from the command line or from PowerShell:

>

To upgrade CS-Script.Core, run the following command from the command line or from PowerShell:

>

To uninstall CS-Script.Core, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade cs-script.core -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade cs-script.core -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure cs-script.core installed
  win_chocolatey:
    name: cs-script.core
    state: present
    version: 2.0.0.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'cs-script.core' do
  action    :install
  version  '2.0.0.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: cs-script.core,
    Version: 2.0.0.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller cs-script.core
{
   Name     = 'cs-script.core'
   Ensure   = 'Present'
   Version  = '2.0.0.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'cs-script.core':
  provider => 'chocolatey',
  ensure   => '2.0.0.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install cs-script.core version="2.0.0.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 23 Feb 2021.

Description

CLR based runtime environment for executing scripts written in ECMA-compliant C#.
The main idea of CS-Script is to allow "plain vanilla" C# code execution from both command-prompt and form any CLR application hosting the script engine.
CS-Script targets .NET 5.
The default installation directory is "%ChocolateyInstall%\lib\cs-script.core".
This package contains the set of scripts and binaries that required for the default functionality. However there is some additional content that represents somewhat less mainstream functionality and experimental features. This content is available as an Extension Pack from the releases page(https://github.com/oleg-shilo/cs-script/releases). Installing the Extension Pack is as simple as downloading and extracting the archive to your chocolatey install location (most likely C:\ProgramData\chocolatey\lib\cs-script.core\tools\cs-script.core).


tools\chocolateyInstall.ps1
$packageName = 'cs-script.core'
$url = 'https://github.com/oleg-shilo/cs-script.core/releases/download/v2.0.0.0/cs-script.win.v2.0.0.0.7z'

try {
  $installDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

  $cheksum = 'FE7079CC71AEA4CDD84090942DDCD0364C6A560A95620E0CF3494F2EB9A640F1'
  $checksumType = "sha256"

  function stop-server
  {
     param(
       $server,
       $port,
       $command
     )

    try {

        $client  = New-Object Net.Sockets.TcpClient($server, $port)
        $socketStream  = $client.GetStream()

        [Byte[]]$Buffer = [Text.Encoding]::ASCII.GetBytes($data)


        $socketStream.Write($Buffer, 0, $Buffer.Length)
        $socketStream.Flush()
    }
    catch{
    }
  }


  stop-server "localhost" "17001" "-exit" # prev release Roslyn compiling server requires "-exit"
  stop-server "localhost" "17001" "-stop" # starting from .NET 5 release CodeDom build server requires "-stop"

  # Download and unpack a zip file
  Install-ChocolateyZipPackage "$packageName" "$url" "$installDir" -checksum $checksum -checksumType $checksumType

  Install-ChocolateyEnvironmentVariable 'CSSCRIPT_DIR' $installDir User
  Install-ChocolateyEnvironmentVariable 'CSSCRIPT_ROOT' $installDir User
  
} catch {
  throw $_.Exception
}
tools\chocolateyuninstall.ps1
$packageName = 'cs-script.core'

function stop-server
  {
     param(
       $server,
       $port,
       $command
     )

    try {

        $client  = New-Object Net.Sockets.TcpClient($server, $port)
        $socketStream  = $client.GetStream()

        [Byte[]]$Buffer = [Text.Encoding]::ASCII.GetBytes($data)


        $socketStream.Write($Buffer, 0, $Buffer.Length)
        $socketStream.Flush()
    }
    catch{
    }
  }


stop-server "localhost" "17001" "-exit" # prev release Roslyn compiling server requires "-exit"
stop-server "localhost" "17001" "-stop" # starting from .NET 5 release CodeDom build server requires "-stop"

Write-Warning "REmoving 'css' shim $($env:ChocolateyInstall)\lib\cs-script.core\tools"

Uninstall-BinFile "css1" "$($env:ChocolateyInstall)\lib\cs-script.core\tools\cscs.exe"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
CS-Script.Core 1.4.5.0-NET5-RC5 23 Saturday, January 23, 2021 Approved
CS-Script.Core 1.4.4.0-NET5-RC4 17 Sunday, January 10, 2021 Approved
CS-Script.Core 1.4.2.0-preview 29 Monday, October 19, 2020 Approved
CS-Script.Core 1.4.1.0-net5-preview 49 Saturday, August 22, 2020 Exempted
CS-Script.Core 1.4.0.0 101 Thursday, July 30, 2020 Approved
CS-Script.Core 1.3.2.0 62 Sunday, May 31, 2020 Approved
CS-Script.Core 1.2.2.0 231 Saturday, October 5, 2019 Approved
CS-Script.Core 1.2.1.0 81 Wednesday, June 26, 2019 Approved
CS-Script.Core 1.1.1.0 95 Wednesday, May 22, 2019 Approved

Release v2.0.0.0

CLI

- New commands:
-server - for managing build server
-vscode - to open script in VSCode
-vs - to script project in Visual Studio
-self-test - for testing the engine on the target system
-self-exe - for building css launcher for manual deployment
-engine:<csc|dotnet>
-new:toplevel - CLI parameter
-profile - for testing script loading performance
-speed - for compiler performance testing
- Added css
- Added creation of code.header on first use of CLI command -code
- Added complex (multi-file) commands support (e.g. css -self-test-run)
- Implemented build server
- Implemented hot-loading for csc engine.
- Normalized all \n and \r\n CLI output by using Environment.NewLine
- Added reporting using of incompatible csc compiler for scripts requiring XAML compilation

CSScriptLib

- Implemented //css_winapp for WinForm and WPF applications
- Added //css_engine (//css_ng) directive for choosing the compiling engine
- Completed CSScript.Evaluator.CodeDom interface.
- Implemented transparent hosting of CSScriptLib in .NET-Framework and .NET-Core
- Removed dependency on Roslyn for pure CodeDom evaluator use-case
- added sample with downloading the latest C# compiler
- added passing compiler options
- Implemented probing for default C#5 compiler when hosted on .NET Framework.
- Extending u-testing to cover new Evaluator features (CSScriptLib.dll)

Discussion for the CS-Script.Core Package

Ground Rules:

  • This discussion is only about CS-Script.Core and the CS-Script.Core package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or CS-Script.Core, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus