Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

129,433

Downloads of v 0.17.1:

77,022

Last Update:

23 Feb 2017

Package Maintainer(s):

Software Author(s):

  • Glenn Block
  • Filip Wojcieszyn
  • Justin Rusbatch
  • Kristian Hellang
  • Damian Schenkelman
  • Adam Ralph

Tags:

roslyn csx script scriptcs

ScriptCs

  • 1
  • 2
  • 3

0.17.1 | Updated: 23 Feb 2017

Downloads:

129,433

Downloads of v 0.17.1:

77,022

Maintainer(s):

Software Author(s):

  • Glenn Block
  • Filip Wojcieszyn
  • Justin Rusbatch
  • Kristian Hellang
  • Damian Schenkelman
  • Adam Ralph

ScriptCs 0.17.1

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install ScriptCs, run the following command from the command line or from PowerShell:

>

To upgrade ScriptCs, run the following command from the command line or from PowerShell:

>

To uninstall ScriptCs, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade scriptcs -y --source="'INTERNAL REPO 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 scriptcs -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install scriptcs
  win_chocolatey:
    name: scriptcs
    version: '0.17.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'scriptcs' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.17.1'
end

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


cChocoPackageInstaller scriptcs
{
    Name     = "scriptcs"
    Version  = "0.17.1"
    Source   = "INTERNAL REPO URL"
}

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


package { 'scriptcs':
  ensure   => '0.17.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 08 Jul 2020.

Description

Write .Net apps with a text editor, NuGet, and the power of Roslyn!


tools\Autofac.dll
md5: D925050321936F415C557BFACC5D9F32 | sha1: E0B9E78C3B3737C2000A830590B58EE671D7B961 | sha256: CE02FBEEDABF893E687069A7D8142F36C9DA2BF02B64FE1E24CE613DBDF0C9DD | sha512: 0971ED3C790B68ACD0137F920E2B865B82500F770164EE92B0A4DA881AC1124F7CD84D54BFF6B86BDDA2430FCEA87B0FC0E7E86A4FA648572120F7FFB983EB95
tools\Autofac.Integration.Mef.dll
md5: 8BFA67721A2A2333C58082D7257FF1F6 | sha1: 92BB73423C75EE081AF064DA99A8E17F62CB414D | sha256: 1677D0CE3B15A6F03D65A6C243493549F3A36CBF2047E6E7997A29D40BD0DA7A | sha512: 7F18FCA0D5E6C9CBEB5727E1D8650E5F0471D2696F88056D05DCBB649100D2CCB6DD33E697B981A828C31C228702AEB8025001036926034F30FAACC82D1C27E9
tools\chocolateyInstall.ps1
try {
    $tools = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

    if (Test-Path "$tools\..\lib") {
        Remove-Item "$tools\..\lib" -Recurse -Force
    }

    # Handle upgrade from previous packages that installed to the %AppData%/scriptcs folders.
    $oldPaths = @(
        "$env:APPDATA\scriptcs",
        "$env:LOCALAPPDATA\scriptcs"
    )

    $oldPaths | foreach {
        # Remove the old user-specific scriptcs folders.
        if (Test-Path $_) {
            Remove-Item $_ -Recurse -Force
        }

        # Remove the user-specific path that got added in previous installs.
        # There's no Uninstall-ChocolateyPath yet so we need to do it manually.
        # https://github.com/chocolatey/chocolatey/issues/97
        $envPath = $env:PATH
        if ($envPath.ToLower().Contains($_.ToLower())) {
            $userPath = [Environment]::GetEnvironmentVariable("Path","User")
            if($userPath) {
                $actualPath = [System.Collections.ArrayList]($userPath).Split(";")
                $actualPath.Remove($_)
                $newPath =  $actualPath -Join ";"
                [Environment]::SetEnvironmentVariable("Path", $newPath, "User")
            }
        }

        Write-Host "'$_' has been removed." -ForegroundColor DarkYellow
    }
    Update-SessionEnvironment
    # End upgrade handling.

    Write-ChocolateySuccess 'scriptcs'
} catch {
    Write-ChocolateyFailure 'scriptcs' "$($_.Exception.Message)"
    throw
}
tools\Common.Logging.dll
md5: A374D30EAA4F0A4B7C09DA2768939C71 | sha1: E84A79B9EF2F8A310D16EA7639AE060090D3DA6B | sha256: D6461B8C61B72AD7EF45505D61965533823C8EFD7D4121FF54AAE7FF2C6F51C4 | sha512: 3A7D62F5C754B3352661699B5F138A64BEF2990BB6218D0017193A9066E6B5AEEF429A08D0DBE68D56B1125DFE761118731F2165C68F205B7339CEE43CE531EC
tools\ICSharpCode.NRefactory.CSharp.dll
md5: 2CDC5C01A85384D194DBF8E5E60F573F | sha1: AF37273253BF02C19ABC9F9A3EC95170629A1DA4 | sha256: 8EFFED61FE7DEC29F30C00BA9E4319FD3D3EDFD36A3368FC9F84501B74A35BE9 | sha512: 5AE110D487DC799BA75514F30981B2290F5FA4BFF32A432DDDD146E934316A30BA837AEBA8B637564E010CE332BF2B09743B3BE3AF30F630DFC0CDADA3A3E41A
tools\ICSharpCode.NRefactory.dll
md5: BCE3311FB49CDD5FE844460397880205 | sha1: 55036269D87BBD15D9DDB00B43880B82CBE37397 | sha256: E5A4124377FE0E473E8D16D452A3BCC6FA8930746ACA266A75CDCDC766E316A1 | sha512: 8886B52E744C395B175EB9EE0B739F59D8BC8781F8F205303C8FB4F8E5B4F3C31BD8463ACDA8E31469915D6D878A8D1B30C48F672AC83CAEC1B7B91147825239
tools\Microsoft.CodeAnalysis.CSharp.dll
md5: 454CAB3DD64B2053B2F7595A4A64E111 | sha1: B05D51269020780A413467E4C78E84F256A4A238 | sha256: 6CC577CE696B2CBBF75068FE8B1F05531EF0BE24A5612EA6D4F1389B09CAF54A | sha512: 7D522A46AEF1588C5CB156FC78DC8B811D45FA7167523D74DA2328236A5E85AA2ABC039FFC0FF350977AD5C39A03D46C99AF486594C06B3435159148B523F548
tools\Microsoft.CodeAnalysis.Desktop.dll
md5: 290C056D387AD34F45709CACE4324B46 | sha1: 2DE65FAEFA695322F806FE1D1685C990C459C6C3 | sha256: 88A247C36800DD587A23105FFA689CB9893CA128B9B3CE9804DE26D7E03B9201 | sha512: E6B468DE80265E7B7E94E04FBC3A967AB9E7759866AE1F2B952D1F289A7393C91D8669EF7785F4DDE3762EB476F65131B780A5B2980EE6A736D6CE80C73D8E04
tools\Microsoft.CodeAnalysis.dll
md5: F245BD815C283F0FBB7FD255E97BF08F | sha1: BC61BD7368DD3C99582BCBBE68D8C23EC9A5252A | sha256: 4B52B899EDB6F665C24A97AC94FA03488E03180507FE31874EC4D8D0AB9F7F91 | sha512: 281B01482A4EAEB149CBF73F92119477468FF75411ABEA564125C8C3EB392E71C6EB7355C0CEF818A3E319F61417DA74A7D71EAE6B01D891DE8BF42C03001D83
tools\Microsoft.CodeAnalysis.Scripting.CSharp.dll
md5: 46E6ED87AF8DB4C45A320D4EAB02B606 | sha1: 518E7BA80983E58D1B936D2E420639375C2BD8BE | sha256: 03F3949278C848688D77878A60A0A26C47FA349B5196E5AB39447D73F549F270 | sha512: CE583F72813D5F64A24D6A27A498B552C55D24BEC3FA12B634B69CDF20DB68C12B7846451305B175BC0329FD484788456094DF2B3A6F4EBB045162BDC9B6AF6C
tools\Microsoft.CodeAnalysis.Scripting.dll
md5: 76236B406E23422AE697BEAAE215A865 | sha1: 0C54E08B931BAB18A1B098693148EF6135BF946B | sha256: 25F8915FE0A82CECAC2EA8B12D668E51B4807DAFD287D678BC164E753C4984CF | sha512: 7C78F0D772154189DB91A4F22CF8EF3F5B67E0F9A57A0380F16EC9099E0BE5DBA2F7B0F16E8B644AE902FF6F561D4189127882E393C3AB5C462AAF2CF1C58179
tools\Microsoft.Web.XmlTransform.dll
md5: A21A47E1C885E2A6BF493D5D76919F1E | sha1: CD9218E56616C16BCCD88EF7BFABE3CE960A7589 | sha256: 0252E8888DFA40D779FF2DF2F2C74CCEFA288471B41FE9534DAA12E805CDA339 | sha512: 9DBA5DE16B8A335E7B8E87874EC06F3C1CB10A093109990B10F19EEFA8616F69E675144E5FB0F445E5418F9EDF1B6F27B1712816CBCCCE6B17D95BC0DBC2C3DF
tools\Mono.Cecil.dll
md5: B1C7DA53F32E6425B84C118047FDFAB4 | sha1: 643D8531AE4E924B57066778883CAEC4ED7F8F4B | sha256: AE75BF2566A936B86BEF42731F1EF32D17B4D496931AD8278D07B9B5076DEF1D | sha512: D6F3DB75672CEF693CD6249DF999C4BA6106CCDB1AADE534D2CD55BCA87899826209109C4191F33E2C6CA6E072F2774EB6CD093BEDFD4B6BC005B68214BACFF9
tools\Mono.CSharp.dll
md5: 9F3473D035062CD546F30E54233A9A7B | sha1: 9613F367AC7340C01B7A8665B1CCE0483F6CE793 | sha256: 80C8ECC58E3140F0EE336292165BF2B887A000014C7DE420B70EEFE4D5E68BCC | sha512: FBA700603756B79BB671080D09081C3F39203F729A749993DF41AD8F68F06FB5CCFCA185AD8DEC25831BE17A61128E57ABE1626CEC77BE6ED20395026C9589A1
tools\Newtonsoft.Json.dll
md5: A94583EE47F673118B0BF822BF8E425D | sha1: BB1FB9C4D6D3B4539569E0051D66C2C6F029A895 | sha256: 030E739CBA60C3B4604EE1574497AEBC892B7CEB0CE44DD39FD1EF7767A2F134 | sha512: 39DCBA07CD4F854982E21FCB7024BD47794E53FC0CB5923757A57AB3FDE64ACFA6076123C8F00A7186C3DC782947473705C8B7933B99172A448F9E615AFFE8D1
tools\NuGet.Core.dll
md5: CFE27B330347673C5EB1387C16F9B69B | sha1: AFD5E99854485B34559D9E122D452563AFAD0A82 | sha256: 784D2A3D7FBDB469CC3A67091763AADF283575A9BF3B873F771F5F87ED7327C7 | sha512: 4F4D9FC6A32EEE2EA52085580993645B651EBA2137A985E03D05645CB8A428840246430FA7EA1D080AB0042EEAB6E84E7BAF72A0C4E8515CCF03274063BAE64C
tools\PowerArgs.dll
md5: DF70C772FDB43E16D7EB192F2197E60E | sha1: 0B15E28EC7ACEE05E0E8AED6EB1CC0087D148261 | sha256: 40ABBB6A93AE34654FFB5177C1B5412123B8863385BC61B4374E6E027F49DB31 | sha512: 67C7441A0F6925FDC3D07CAA6549AD4ED5BFB1E3696EBE66AF8F8A6A78902F572CC401370D8DE539220B84548A9CAD773D769939F8CD28A7686321DF9DFD5DB6
tools\ScriptCs.Contracts.dll
md5: B560373CFBFD3DF1A80002CA1096AEE3 | sha1: CA54D236B3D02503847C5245758E5DA05A3B1028 | sha256: 12C4825351677DE3A2215710F0C26B6A7D7E7AD33410A9674CB2FF8F8DBBB6C6 | sha512: 6FEB8D3121F9C10F9DE1918DD0C32B248A54BF47922A4CED682DE47BA766747371AE91736DDF6CBB8A70BDE859AF437121BF750248E62DD445261EABE19DF93C
tools\ScriptCs.Core.dll
md5: A957B2EAC60199FE99F6D62858739AD7 | sha1: 2D44BD0B34B4ECA5B18076C8FED96C12045B430B | sha256: 462B8D79C1FFF1A1CE273EF3F70CF08D018C7AC8DBCC97F92978937E7EEFB6B6 | sha512: 0D1DB40BB74210F4DFB784C87411AE8B52F27CF135A8A98A3A3C7E2E79F51C2B2BEBF98E9729B4439EC97B6EE9994C94E21546C444DCD134569614AB83FEC815
tools\ScriptCs.Engine.Mono.dll
md5: 46A687185646B8FC9EE6AEA9870212A6 | sha1: 87857079DA01220181B92B4497A5AB206ABE5945 | sha256: 8579CEE3AB1C604572C8C95A6188AB707EF00A11E9DC76D201E844347A6DD934 | sha512: 4FA2C00FF7A4930F86606CC5148D6509B553FFEDE634B89ACBF44D14CAD2A701482546B1A3C6DEE1004C2A03ED17222A2A879C9288263FB53AF30FDA00B8F459
tools\ScriptCs.Engine.Roslyn.dll
md5: 1A0CCD659382CF79607B945D9934B86E | sha1: E3547074C279A1B0692AD66208B76A0B9154B589 | sha256: 895365F318CD88D2B2FA82C3401659CE46DD8FD44BB11E69F7A3409271ED718C | sha512: B8F2C728FFA173660EEF237017A10F815D71BD03DBA4A583475C9D3F1C54EDAEFD8637F05F4EB6C54BBA5BD76AC4802C679A978E82412B61F4F61F413CA64C44
tools\scriptcs.exe
md5: A572DD1F8E2FC349AE8130C61CFB960D | sha1: DF6C26BE3D042D18BFFA5D1D8D5D8AD2A30FE1EF | sha256: 5AA6413FCFD700D6926560468401A6AC2C0B6115AF3F8407401604960EBE986E | sha512: 5A7453EC09EDE41E8B81FDA80AC8BA5483B7191CEF7B54DD083319534D17893B06F2E9C0EE5E0E85D1D17A1650A7BEE242C674C7BE00D67B2790F59602A82DD2
tools\scriptcs.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
</configuration>
tools\ScriptCs.Hosting.dll
md5: C54E35322B5CFBC5C01F0CA4152E44BE | sha1: 8C3DB16D2529CBCAD026E24AC08E203F676E1094 | sha256: C32C6143553C7BF68C0CC48E4B38B60FE212502764FA10D15676ECA37D1B7067 | sha512: 38289830759B86F09A49921B16BE7ECCD553B2689DF591584B634E47E20BD8BA529EBD340EECED14F75D5A189B028C968632C497DAFE94E1C016E64225225971
tools\System.Collections.Immutable.dll
md5: 39C38A23F07DF952F90FC8C0045047A7 | sha1: CB1ADD24A135B67B26766B0D078DE784AFE27725 | sha256: 7AF2DA909BBCE16013A79B91F868ABB2A7829667D6E9A73B44FDACFBD77117A5 | sha512: C05F3A555AB11065DB17DCCA9FA953D84178B11108116D29671FFBDF80BEC9D463FA6BE6D0B112952613430E024CE0D5F05147985901E34141EC599C2EACE664
tools\System.Reflection.Metadata.dll

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.

Add to Builder Version Downloads Last Updated Status
ScriptCs 0.17.0 1504 Monday, February 13, 2017 Approved
ScriptCs 0.16.1 7471 Thursday, April 7, 2016 Approved
ScriptCs 0.16.0 945 Saturday, April 2, 2016 Approved
ScriptCs 0.15.0 6949 Monday, August 3, 2015 Approved
ScriptCs 0.14.1 3902 Sunday, April 12, 2015 Approved
ScriptCs 0.14.0 1225 Monday, March 23, 2015 Approved
ScriptCs 0.13.3 2027 Tuesday, February 24, 2015 Approved
ScriptCs 0.13.2 1152 Saturday, February 7, 2015 Approved
ScriptCs 0.13.1 643 Thursday, February 5, 2015 Approved
ScriptCs 0.13.0 902 Wednesday, January 28, 2015 Approved
ScriptCs 0.12.0 1444 Wednesday, December 24, 2014 Approved
ScriptCs 0.11.0 870 Thursday, December 11, 2014 Approved
ScriptCs 0.10.2 3811 Friday, August 1, 2014 Approved
ScriptCs 0.10.1 662 Wednesday, July 30, 2014 Approved
ScriptCs 0.10.0 762 Wednesday, July 30, 2014 Approved
ScriptCs 0.9.0 5134 Friday, February 7, 2014 Approved
ScriptCs 0.8.1 3444 Saturday, October 12, 2013 Approved
ScriptCs 0.8.0 1073 Wednesday, September 18, 2013 Approved
ScriptCs 0.7.0 1085 Thursday, August 15, 2013 Approved
ScriptCs 0.6.0 844 Monday, August 5, 2013 Approved
ScriptCs 0.5.1 1532 Sunday, June 16, 2013 Approved
ScriptCs 0.4.0 1533 Monday, May 13, 2013 Approved
ScriptCs 0.3.2 1063 Wednesday, April 17, 2013 Approved
ScriptCs 0.3.1 635 Wednesday, April 10, 2013 Approved
ScriptCs 0.3.0 633 Tuesday, April 9, 2013 Approved
ScriptCs 0.3.0-alpha-130315 643 Saturday, March 16, 2013 Approved

This package has no dependencies.

Discussion for the ScriptCs Package

Ground Rules:

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