Get it via svm or Chocolatey! Homebrew PR pending.

Special thanks to: @BlackFrog1, @gregoryyoung, @aarondandy, and @rickardp for their contributions to this release.

This Release

This is the first release in a while for scriptcs. It includes some great new features such as Pretty Printing, Support for NuGet credentials, enrichment to the execution environment and more!

For API users (hosting or other programmatic usage), there is one major change, the removal of members exposing Common.Logging types (#1189) from the public API. These were deprecated in version 0.15.0. As a result, the ScriptCs.Core NuGet package no longer takes a dependency on the Common.Logging package.

Breaking API Changes

High impact: Common.Logging types have been removed from the scriptcs public API.

Medium impact: The ScriptCs.Core NuGet package no longer takes a dependency on the Common.Logging package. If you are using Common.Logging for other purposes, after upgrading your project to ScriptCs.Core 0.17.0 you should check to see if NuGet has removed Common.Logging. If so, you will have to reinstall it yourself.

Low impact:

Affects hosters / module authors only

• The IConsole interface has a new Width parameter.
• The IScriptEnvironment interface has new members AddCustomPrinter<T>), Print<T>(), ScriptPath, LoadedScripts, ScriptAssembly, and Initialize().
• The FileParserContext and FilePreProcessResult classes have a new member: ScriptPath

Issue Details

New Features

• Common Logging is gone! (Sending Common.Logging to oblivion! #1190) - by @glennblock. Kudos to @adamralph for getting everything in place to allow the surgical removal.
• Pretty printing support has now been added to the REPL (Pretty Printing #1156) - by @gregoryyoung

![screen shot 2017-02-11 at 10 46 24 pm] (https://cloud.githubusercontent.com/assets/141124/22864844/8de41d34-f10d-11e6-9f9a-5091f5a42812.png)

• You can now access the main script and any loaded script paths using the new Env.ScriptPath and Env.LoadedScripts properties (Access currently running (or possibly main) script #225) - by @glennblock

• You can access the compiled script assembly from within a script using the new Env.ScriptAssembly property. This alleviates having to use reflection or jump through hoops to get the script assembly (Expose a reference to the current script assembly #244) - by @glennblock

  #load child.csx
  Console.WriteLine("Main script:" + Env.ScriptPath); 
  Console.WriteLine("Loaded scripts:");
  Console.WriteLine("\t" + String.Join(Environment.NewLine + "\t", Env.LoadedScripts.ToArray()));  
  Console.WriteLine("Assembly:" + Env.ScriptAssembly);

  

• Added a ScriptCs Nuget package which has all the binaries. This allows running scripts like on a CI server simply by installing the package from NuGet. Also makes it easy to include ScriptCs binaries in a project. (Publish scriptcs.exe as its own nuget package #1061) - by @glennblock

• Added new -e and --eval options for allowing execution of code passed at the command line. (Currently does not work with svm due to a bug) (Allow passing code to scriptcs at the command line #1085) - by @glennblock

  

• Global Credential provider can now be set for NuGet. (Use packageSourceCredentials when interacting with feeds #1018) - by @aarondandy

Fixes

• REPL command help displays formatted to the width of the terminal. (Word wrap the Repl Command description in the Help Command #1047) -by @BlackFrog1

  

• Char literals are properly handled if they have escape chars. (The Mono engine is unable to handle escape sequences in char literals #1143) - by @rickardp

• Compilation into cache no longer throws a ScriptCompilationException (Compilation into cache leads to ScriptCompilationException #1153) - by @filipw

• Stylecop removed from test projects, LibLog and Mono LineEditor (Fixing StyleCop issues. Removing StyleCop form tests. Also adding Sty… #1191) - by @glennblock

• Changed errors to always show in Red as opposed to Dark Red to address readability (Is there a way to change the colors for output? #1198) - by @glennblock

  

• Comments can now be before directives. (Comments in the head of a script file must not throw the error "Encountered directive after the start of code" #1185) - by @glennblock

• Relative paths are now handled properly (When launching a script using a relative path, the working directory is the current path NOT the script path #1193) - by @glennblock

• Updated to Nuget.core 2.14.0 fixes error with ScriptCs.OctopusClient script pack (Updating to Nuget.Core 2.14.0 #1208) - by @glennblock