Release v2.0.6.0

• Integration with the external .NET Tools CS-Script and Syntaxer is now the only integration option.
  This change is to ensure the plugin is always integrated with the latest internally compatible CS-Script tools.
• You can always integrate the plugin with the latest CS-Script tools by running the Detect and Integrate command from plugin's Config Dialog.
• If you do not have CS-Script tools installed you can single-click deploy them form the 'Update' tab of the Confog dialog.
• The .NET Tools manager is made the default deployment option for CS-Script and Syntaxer
• Embedded CS-Script engine is no longer distributed with the plugin.

Release v2.0.5.0

• Embedded CS-Script engine is updated to v4.8.16.0
• Configuration Dialog: Added support for installing external CS-Script engine from WinGet and NuGet.
• Updated plugin hosting solution to address the Scintilla .NET Interface issue (#74).

Release v2.0.4.0

• Fixed #74: Intellisense not working as expected.
  Added workaround for the ricent Scintilla changes around SciMsg.SCN_CHARADDED notifications.
• The default of AutoSelectFirstSuggestion is changed to true. To make it consistent with VS. It can always be changed in the config file.

Release v2.0.3.0

• Npp compatibility checking (Issue #64) is disabled in favor of hard-codded compatibility for new Scintille.TextRange API.
  The checking algorithm became fragile in the latest releases of NPP when the editor restarts itself in Admin mode.
• Updated CS-Script embedded engine to v4.6.4
• Updated CS-Script.Syntaxer embedded executable to v3.1.2

Release v2.0.2.0

• Improved Npp compatibility checking (Issue #64)
  #64 (comment)

Release v2.0.1.0

• Improved Npp compatibility checking (Issue #64)
  Described: #64 (comment)

Release v2.0.0.0

This is the first release of the plugin purely targeting .NET 6 and higher.

New features and changes:

• The plugin requires .NET 6 or higher to be installed on the target system for scripts to be run.
• It is possible now to integrate the plugin to use a custom version of CS-Script and syntax services (e.g. installed from Chocolaty).
  You can do it from the settings dialog.

New limitations:

• If you need your scripts to target .NET Framework then you will need to install the older version.
  v1.7.29.0: https://github.com/oleg-shilo/cs-script.npp/releases/tag/v1.7.29.0
  If you only need to use .NET Framework assemblies from your script you can rely on .NET bridge mode available with .NET Core runtime (e.g. WPF under .NET Core).

Some plugin legacy features are no longer available:

• All Debugger features are removed.
  This is because the .NET debugger available in previous releases does not support .NET Core runtime.
  Use external debuggers instead ("Debug" button on CS-Script toolbar)
• The interception of the Debug output of the script is removed.
  This is because the .NET Core runtime no longer supports this technique.

Release v1.7.29.0

Release v1.7.29.0

The API workaround is not backwards compatible due to the technical limitations of Notepad++ plugin distribution model. Thus CS-Script enables/disables the workaround depending on the detected version of Notepad++. Meaning that the user experience is seamless, all versions of Notepad++ prior v8.3.0 disable the workaround, while v8.3.1 and higher enable it.

Please be aware that Notepad++ team does not coordinate their releases with the plugin authors so you may find that the future Notepad++ releases may become broken, thus if you see a specific future version of Notepad++ is crashing when you try to use CS-Script, please report it and a hotfix will become available very quickly.

You can always overwrite the auto-enabling API workaround algorithm by setting environment variable

• CSSCRIPT_NPP_NEW_NPP_API= "true" - new API enabled
• CSSCRIPT_NPP_NEW_NPP_API= "false" - new API disabled
• CSSCRIPT_NPP_NEW_NPP_API=<not set> - new API will be enabled if Npp is v8.3.1 and higherd

Huge thank you to rdipardo for the investigation and the actual solution.

Note: this release has been tested on Notepad++ v8.2.1 and v8.3.1

---

Changes

v1.7.29

• Added transparent switching to the new NPP API depending on the version: v8.2.1<->v8.3.0 (triggered by #64 and #65)
  Note: the trigger has been changed from v8.3.1 to v8.3.0 due to the N++ team decision to declare v8.3.0 as a current critical release.

v1.7.28
The major feature of this release is the workaround breaking API changes introduced in at least v8.3.1 of Notepad++.

• Patched NppPluginNet: CharacterRange.cpMin and CharacterRange.cpMax changed from int to IntPtr
  This addresses the problems triggered by this the third-party component (NppPluginNet):
  • Issue #64: Creating a new script crashes latest 64-bit Notepad++ release
  • Issue #65: Intermittent crashes (and the culprit is CS-Script)
• Added logging syntaxer internal errors to the plugin log dir.

Release v1.7.28.0

The major feature of this release is the workaround breaking API changes introduced in at least v8.3.1 of Notepad++.

The API workaround is not backwards compatible due to the technical limitations of Notepad++ plugin distribution model. Thus CS-Script enables/disables the workaround depending on the detected version of Notepad++. Meaning that the user experience is seamless, all versions of Notepad++ prior v8.3.1 disable the workaround, while v8.3.1 and higher enable it.

Please be aware that Notepad++ team does not coordinate their releases with the plugin authors so you may find that the future Notepad++ releases may become broken, thus if you see a specific future version of Notepad++ is crashing when you try to use CS-Script, please report it and a hotfix will become available very quickly.

You can always overwrite the auto-enabling API workaround algorithm by setting environment variable

• CSSCRIPT_NPP_NEW_NPP_API= "true" - new API enabled
• CSSCRIPT_NPP_NEW_NPP_API= "false" - new API disabled
• CSSCRIPT_NPP_NEW_NPP_API=<not set> - new API will be enabled if Npp is v8.3.1 and higherd

Huge thank you to rdipardo for the investigation and the actual solution.

Note: this release has been tested on Notepad++ v8.2.1 and v8.3.1

---

Changes

• Patched NppPluginNet: CharacterRange.cpMin and CharacterRange.cpMax changed from int to IntPtr
  This addresses the problems triggered by this the third-party component (NppPluginNet):
  • Issue #64: Creating a new script crashes latest 64-bit Notepad++ release
  • Issue #65: Intermittent crashes (and the culprit is CS-Script)
• Added transparent switching to the new NPP API depending on the version: v8.2.1<->v8.3.1 (triggered by #64 and #65)
• Added logging syntaxer internal errors to the plugin log dir.

Release 1.7.27.0

This release is only compatible with Notepad++ v8.3.1 and higher.

Huge thank you to rdipardo for the investigation and the actual solution.

• Patched NppPluginNet: CharacterRange.cpMin and CharacterRange.cpMax changed from int to IntPtr
  This addresses the problems triggered by this the third-party component (NppPluginNet):
  • Issue #64: Creating a new script crashes latest 64-bit Notepad++ release
  • Issue #65: Intermittent crashes (and the culprit is CS-Script)
• Added logging syntaxer internal errors to the plugin log dir.