Skip to content

Latest commit

 

History

History
202 lines (136 loc) · 8.26 KB

CHANGELOG.md

File metadata and controls

202 lines (136 loc) · 8.26 KB
Raw

Change Log

2.2.3 (20 Jul, 2024)

  • #39: Run in Terminal Button doesn't work

2.2.2 (20 Jun, 2024)

  • Updated CS-Script (v4.8.16) engine and CS-Syntaxer (v3.1.4)

2.2.1 (8 Jan, 2023)

  • Updated CS-Script (v4.6.2) engine and CS-Syntaxer (v3.1.1)

2.2.0 (31 Oct, 2022)

  • Added command CS-Script: Reset busy status. It's useful for cases when the script execution hangs for whatever reason.
  • Issue #33: Does not work with non-ascii characters in file or folder names.
  • Fixed copying .vscode folder on cs-script.load_project command when external CS-SCript deployment is used.
  • Fixed problem with JS object not being properly cast to TS Settings type instance (utils.ts)
  • Added unconditional exception handling for syntaxer communication failures (syntaxer.ts)

2.1.0 (6 Apr, 2022)

  • Updated CS-Script engine and Syntaxer to target .NET 6
  • Removed all obsolete (e.g. Mono) settings
  • Added the following settings to allow re-targeting the extension to the external (not embedded) engine (cscs.dll) and syntax service/provider (syntaxer.dll)
    • cs-script.engine.cscs_path
    • cs-script.engine.syntaxer_path
    • cs-script.engine.syntaxer_port
  • Created wiki to help setting up the environment for the CS-Script CLI integration with the major IDEs like VS Code: https://github.com/oleg-shilo/cs-script/wiki/CLI-Environment-Specification

2.0.1 (20 Sep, 2021)

  • Updated CS-Script engine and Syntaxer
  • Addressed GitHub flagged vulnerability concerns
  • Extra arguments to be always passed to the script engine (e.g. -cd for treating script as a dll source file). It allows addressing inconvenience of "Issue #26: Check syntax in scripts lacking Main method"

2.0.0 (30 Jan, 2021)

This release delivers hosting script execution under .NET5.

  • Migrated on CS-Script.Core v1.4.5 targeting .NET 5

1.6.0-4 (11 Apr, 2020)

This release delivers hosting script execution under .NET Core. Meaning that raw VSCode deployment with the extension extension "ms-dotnettools.csharp" is enough to edit, run and debug C# script. Mono and Mono extension are no longer required. Mono support is still available via settings but it will be eventually phased out.

  • Migrated on .NET Core
  • Hosting on Mono is still supported. If required it needs to be enabled via settings specific for the type of the activity:
  • cs-script.engine_run.dotnet
  • cs-script.engine_debug.dotnet
  • cs-script.engine_project.dotnet
  • Fixed #21: Removed unnecessary check for presence of Mono
  • Fixed #22: folder runtimes (of the syntaxer) is added to the package
  • Fixed Load Project use-case

1.5.12 (21 Mar, 2020)

  • Issue #20: Extension Stopped Working after "C# for Visual Studio" (dependency) extension update

1.5.11 (17 Feb, 2020)

  • Issue #19: How to Run CSScript in VSCode using latest Extension. Fixed problem with process = exec(command); accidentally modifying global variable process, which was probably introduced in the latest VSCode.

1.5.10 (Nov 30, 2019)

  • Issue #15: CS-Script for VS Code Portable.

1.5.8-9 (Mar 18, 2019)

  • Fixed problem with the "Unable to open" error at startup when open_file_at_startup is set to empty string.
  • Added work around for failure of Roslyn- based ICodeCompiler to run on OSX. Implemented by setting useAlternativeCompiler:none and effectively downgrading C# syntax support to version 6.
  • Fixed problem with Settings not being saved in case of the instance being load from the JSON file.

1.5.7 (Sep 5, 2018)

  • Added support for debugging classless scripts directly (without decorated source file).
  • Added support for freestyle classless scripts without any entry point defined:
    //css_ac freestyle
    using System;
    using System.IO;

    foreach (var file in Directory.GetFiles(@".\"))
        Console.WriteLine(file);

1.5.6 (Jun 26, 2018)

  • Fixed problem with the injected //css_syntaxer directives not being cleared after CS-Script document formatting.

1.5.5 (Jun 26, 2018)

  • Added option to cs-script.enable_code_formatting enable/disable document formatting provider.
  • Added handling the case of MONO being installed but not added to PATH. Note, this only helps for running the scripts but not for debugging, which is handled entirely by VSCode.

1.5.4 (Jun 9, 2018)

  • Added handling/processing unsaved changes in the source files without creating a <file>.$temp$.cs file in the script directory.

1.5.3 (May 15, 2018)

  • Added "!inDebugMode" condition for "cs-script.debug" command.
  • Issue #10: CSSConfig: searchDirs parameter not working.
  • Edit engine setting command now opens both .NET and Mono settings' files

1.5.2 (May 11, 2018)

  • Add option to suppress execute/debug in workspace mode (cs-script.suppress_script_debug_for_workspaces).
  • Add option to tunnel CS-Script StartDebug request to the workspace launch.json algorithm (cs-script.fallback_to_launch_json).
  • Start Debug now activates DebugConsole output panel.
  • Issue #9: Add an option to hide "CS-Script: About" from the context menu.
  • Default CS-Script config file now contains -l switch, which sets the current directory to the location of the script at the start of the execution.

1.5.1 (Apr 29, 2018)

  • Added the logo icon into the package/distro

1.5.0 (Apr 29, 2018)

  • Implemented Intellisense for standalone C# files:
    • Rename symbol
    • Signature help
    • Assignment completion
  • Reduced embedded Roslyn runtime footprint.

1.4.0 (Apr 3, 2018)

  • Implemented Intellisense for standalone C# files:
    • Code completion
    • Go to definition
    • Hover/tooltip
    • Find all references
    • VS style of "Find all references" result in output panel
  • Added VB.NET syntax support (Windows only)

1.3.5 (Jan 1, 2018)

  • Added explicit extension dependency on mono-debug. Seems the disclaimer "to add Mono" in the extension description does not convince users users to do so.

1.3.4 (Jan 1, 2018)

  • Fixed problem project tree not being updated on saving the script.

1.3.3 (Dec 31, 2017)

  • Fixed problem with the original VSCode debugging API being deprecated (vscode.commands.executeCommand("vscode.startDebug") vs vscode.debug.startDebugging(...)).

1.3.2 (Aug 21, 2017)

  • 'Check syntax' action that became in conflict with the new "scripted arg" support.

1.3.1 (Aug 21, 2017)

  • Issue #4: Project fails to load if the script has cs-script directive invalid syntax.
  • Issue #5: Executing detached script (Ctrl+F5) work OK but sometimes trigger "is busy" warning message.
  • Updated cs-script engine to v3.27.3 (assorted Linux improvements)

1.3.0 (Aug 12, 2017)

  • Added project tree view
  • Implemented CS-Script execution with standard F5 via on-fly generated specific launch.json
  • Implemented CS-Script specific intellisense
    • Added 'Go to definition' for CS-Script directives
    • Added auto-completion for CS-Script directives
    • Added auto-completion for path items in CS-Script //css_include directive
    • Added 'on hover' support for CS-Script directives
    • Added "Show project info" tree view button

1.2.1 (Jul 4, 2017)

  • Fixed problem with generating debug info for Mono-Debug on Windows

1.2.0 (Jul 3, 2017)

  • C# 7 support out of box
  • New commands:
    • "help"
    • "build exe"
    • "new script"
    • "run in terminal"
    • "engine settings"
  • Added dedicated toolbar buttons for the most common CS-Script commands.
  • Revoked extensionDependencies to the manifest file. Currently VSCode does not automatically installs specified dependencies but instead silently fails loading the extension if any dependency is not found. This all dependencies in the manifest file are removed so the extension can validate environment and clearly communicate the initialization failure reason(s).

1.0.1 (May 30, 2017)

  • Implemented work around to allow single-step loading of OmniSharp project for enabling Intellisense.
  • Implemented navigation to the file location on a single click (on error info) in the output panel.
  • Added extensionDependencies to the manifest file. This should bring C# and Mono Debug plugins if they are not installed.

1.0.0 (May 27, 2017)

  • Support for C# script execution (with cscs.exe)
  • Support for C# script syntax checking (with cscs.exe)
  • Support for C# script debugging (with Mono Debug extension)
  • Integration with VSCode IntelliSense (with OmniSharp extension)
  • Printing C# script dependencies ('print project' command)