Downloads:

24,456

Downloads of v 3.29.0.0:

620

Last Update:

5/22/2019

Package Maintainer(s):

Software Author(s):

  • Oleg Shilo

Tags:

cs-script C# script dynamic hosting

CS-Script

3.29.0.0 | Updated: 5/22/2019

Downloads:

24,456

Downloads of v 3.29.0.0:

620

Maintainer(s):

Software Author(s):

  • Oleg Shilo

CS-Script 3.29.0.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall CS-Script, 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://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://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade cs-script -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 -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 installed
  win_chocolatey:
    name: cs-script
    state: present
    version: 3.29.0.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'cs-script' do
  action    :install
  version  '3.29.0.0'
  source   'STEP 3 URL'
end

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


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

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


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

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


package { 'cs-script':
  provider => 'chocolatey',
  ensure   => '3.29.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 version="3.29.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.

This package was approved as a trusted package on 7/24/2019.

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 Microsoft implementation of CLR (.NET up to v4.8) with full support on Mono.
The default installation directory is "%ChocolateyInstall%\lib\cs-script".
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\tools\cs-script).


tools\chocolateyInstall.ps1
$packageName = 'cs-script'
$url = 'https://github.com/oleg-shilo/cs-script/releases/download/v3.29.0/cs-script.7z'

try { 
  $installDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  $configApp = Join-Path $installDir "cs-script\Lib\ConfigConsole\ConfigConsole.exe"
  #Write-Host "$configApp"
  $cheksum = '66E11C3C8D095EEC38B73A233777CAAEE17E82E14C35787A0622F32ADFA61285'
  $checksumType = "sha256"
  
  # Download and unpack a zip file
  #Install-ChocolateyZipPackage "$packageName" "$url" "$toolsDir" ["$url64" -checksum $checksum -checksumType $checksumType -checksum64 $checksum64 -checksumType64 $checksumType64]
  Install-ChocolateyZipPackage "$packageName" "$url" "$installDir" -checksum $checksum -checksumType $checksumType
  
  try {
    Stop-Process -Name "VBCSCompiler"
  } catch {
  }
  
  Start-Process -FilePath "$configApp" -ArgumentList "/quiet /nogui"
  
} catch {
  throw $_.Exception
}

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 3.28.9.0 617 Monday, December 10, 2018 Approved
CS-Script 3.28.7.0 461 Sunday, September 2, 2018 Approved
CS-Script 3.28.5.0 289 Thursday, July 19, 2018 Approved
CS-Script 3.28.4.0 480 Saturday, April 28, 2018 Approved
CS-Script 3.28.2.0 496 Thursday, March 15, 2018 Approved
CS-Script 3.27.5.0 731 Monday, August 28, 2017 Approved
CS-Script 3.27.4.0 243 Monday, August 21, 2017 Approved
CS-Script 3.27.3.0 198 Monday, August 21, 2017 Approved
CS-Script 3.27.2.0 256 Friday, August 11, 2017 Approved

Release v3.29.0.0

  • Implemented NuGet dependencies discovery
  • Added support for wildcards in //cssref directive (e.g. //cssref ./*.dll).
  • Added support for -rt:<runtime> switch in //css_nuget directive
  • Added support for //css_nuget source <url>
  • Added migration of old shell extension configuration to Shell-X deployment
  • Issue #149: Suggesting to normalize paths in CompilingInfo.Input
  • Issue #138: Please update WSDL.exe and WSDL.cs to allow for TLS 1.2

This package has no dependencies.

Discussion for the CS-Script Package

Ground Rules:

  • This discussion is only about CS-Script and the CS-Script 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, 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