Snowflake fixes:
================
- Fixed an issue with C# code-behind for Snowflake scripts that use {handler}, {query}, and {function} directives
- Allowed multi-statement SQL scripts

SQLite engine: bringing back column type detection to be able to mark a column as containing dates. SQLite will not prevent other data types from being written into this column but will attempt to return values from it as dates.

SnowFlake: saving Snowflake scripts was broken. Now fixed.

Snippets: Fixed caret position after snippet completion.

ResultViewer: update columns when number formatting setting changes

SQL Preprocessor: fixed an issue with generating C# code from SQL queries with a {query} directive.

SQL Server scripts: additional built-in TSQL functions support in code editor (e.g. isnull)

Fix: SQLite Date Issue
=======================
Fixed an issue with Dates in the SQLite engine (regression). Neither Excel nor SQLite have a dedicated "date" data type; both simulate it using other types. Excel stores date values as double-precision numbers (OAdate), while SQLite can store them in multiple ways, depending on the DateTimeFormat setting in the connection string. In QueryStorm, by default, SQLite stores date values as double-precision numbers (JulianDay). This can be a problem, especially with dynamically generated values, as it's not straightforward to detect when a number returned by the SQLite engine should be treated as a date (and thus should be converted from JulianDay to a date) and when it should be treated as a regular number.

This was previously handled by detecting Excel column types and ensuring any value written to a column that contains only date values (formatted as dates) are converted to a date. This broke in a recent update, which turned off autodetection to enable C# scripts to write values of any type to any column when using the default data context.

In this commit, the SQLite engine gets this auto-detection again but the C# one does not (since C# does have a dedicated datetime type, this is not an issue with it).

Fixed a threading issue in Tabulars

Fix for functions not refreshing on parameter change

Hotfix for streaming functions defined in workbook apps:
They were showing up as #Name error when the workbook initially opened until the user recalculated. Now fixed.

Runtime changes
===============
Streaming functions (like Windy.Query) will now correctly show up when openning a workbook, instead of showing up as #NAME error. Also included is a hotfix for v2.12.517 - after installing an app from the store, functions weren't showing up in tooltips until Excel restart (now fixed).

IDE changes
===========
This version includes an overhaul of ITabular and IDataContext interfaces used extensively through QueryStorm, though mainly under the hood. The main change is that async methods are replacing the previous sync methods. Given that a datacontext and an ITabular represent a snapshot of external data, it is appropriate for the loading and saving operations to be async.

In addition, the SQL preprocessor has been changed to make functions and event handlers fully async. Previously they were sync by default, but it is approprite for DB access to always be async and, in case of event handler, cancellable.

This might unfortunately cause breaking changes in user code. The potential breaking changes are described below:
- The constructor of the WorkbookDataContext class has an additional parameter. This means that if you have a custom data context derived from this classes, you should update the constructor to accept (and forward to the base class constructor) the following parameters: IWorkbookAccessor workbookAccessor, ISyncRunner syncRunner, IWorkbookDataEventsSource workbookDataEventsSource. No other changes are necessary here.
- ITabular and IDataContext interfaces have been updated and are moving away from sync methods. This is unlikely to cause anyone a direct problem as user code usually does not use these directly.
- The "async" keyword has been removed from the SQL preprocessor as all operations are now async. Instead of {async function test()}, you can now write {function test()}, and async is implied. The same goes for event handlers. During execution of an event handler, a modal progress dialog will inform the user of the current operation and allow them to cancel execution. As a result, all SQL scripts that contain {handler}, {query}, or {function} preprocessor directives, MUST BE RE-SAVED to regenerate the codebehind. You can do this by making a trivial change in the script, e.g. add a space to the end of a line and then save the file. Also, any "async" keywords in the SQL preprocessor declarations must be removed.
- support for Google Sheets data contexts has temporarily been removed. If this is causing you problems, please get in touch with antonio@querystorm.com to vote to re-enable this sooner rather than later.
- ITabular now supports a small and fixed number of data types (bool, number, text, datetime, and any). Previously, columns could have been of any type, which was causing conversion issues when comparing data stored in Excel with data coming in from other systems (e.g. Monday.com or AirTable)

Note that this version does not involve breaking changes between apps and the runtime, so old apps will continue working with this runtime version and vice versa.

Installer fix
==========
- The XLL files were not getting signed, so they were getting blocked by some anti-malware programs

Misc
========
- updating SyncFusion components (results grid)
- slight improvement in code editor auto-complete lag

New features
============
- This version adds basic Snowflake support as a new script type. Still missing is a UI to facilitate editing connection strings, as well as proper code analysis. Currently, the SQLite parser is used for code analysis (code completion, error highlighting, etc...), which means that the code editor might highlight errors where there are none (when using Snowflake syntax that isn't valid in SQLite). Improvements in this area will be added over time, as users interact with the initial version and request improvements.


Bug fixes
=========
- issue with returning empty 1d array from functions
- minor UI fixes
- document write times changed from local to UTC

Two problems fixed:
- Fixing Monday.com data context issues
- Fixing installer in-place upgrade issue

Summary
==================
This version mainly includes changes that revolve around building connector apps (e.g. MondayLink, a 2-way connector between Excel tables and Monday.com; for details find MondayLink on YouTube). The logic for building connector apps has been included into QueryStorm to make it easier to build connectors to other systems.

This version also includes a few important bug fixes and a couple of less important ones.

Due to a requirement to allow apps to request different kinds of licenses for different areas, the runtime API has been altered, which results in the breaking change described below.

Breaking change!
================
This version contains a breaking change in the API between the runtime and apps. This means that QueryStorm apps created with this version of the IDE will not run on previous versions of the runtime (2.10 or lower), they will require version 2.11 of the runtime. This change was done to better support the ability to license apps but a minor cleanup of the API was also done since we're already breaking backwards compatibility.

Apps will need to be recompiled with this latest version of the IDE to be compatible with the latest version of the runtime. No changes in code will be required and no behavioral changes should occur as a result.

Other changes:
==============
- added support for cancelling async function execution (previously it continued in the background even if the cell that made the call originally was cleared)
- updating monday.com library to latest API
- fixing a caching issue with tables
- updated (result) grid control to latest version
- minor UI refresh
- fixed issue of duplicate log entries when multiple instances of QueryStom are running in separate Excel windows

This version includes mostly internal changes (code cleanup and refactoring as well as several features needed by some of our built-in apps).

This version includes a series of bug fixes:
============================================
- fix issue with multiple auto-complete dialogs showing for the same code file
- fix issue of the code editor losing focus each time a script is executed (now focus stays on the editor, but the results/message pane still gets brought to front if needed)
- fix issue with functions returning an empty 2d array (was showing up as 0 instead of blank)
- fixed issue with writing large number of guid values to an Excel table
- fixed issue with WorkbookDataStore not saving the timestamp when files change (so workbookdatacontext was always being detected as changed, on each build, even if it is up to date)
- forwarding all trace and console WriteLine calls to the messages pane (runtime, IDE and apps)
- going back to enforcing that apps load their own dlls instead of piggybacking on the runtime's dlls (which might be a different version)
- fixing a bug that was preventing pasting text from the windows clipboard history pane into the code editor using the Enter key (mouse click worked fine).

Hotfix
=====
Fixing Excel interop issue which was introduced in the previous version (v2.10.503)

Other
=====
- additional fix for non-model dialogs e.g. the log viewer in the QueryStorm runtime (fixes issues with keyboard focus, resizing, moving)
- fixing an issue with list of installed packages being wrong when user removes packages and then rebuilds a new one

- Several UI fixes and tweaks
- Fix for "Log viewer" dialog drag/resize freezing windows UI
- Fix for QueryStorm external application shutdown behavior (to avoid leaving excel hanging after close)
- Fix potential deadlock scenarios when debugging with external QS application
- Including missing XML documentation files for QueryStorm

Fixes to the updater
====================
- added text wrapping in the "Summary" field
- separated "Summary" and "Release notes" into two tabs
- fixed hyperlink click behavior
- added icon to releases that have dedicated release notes

External QueryStorm application
===============================
- scripts now work right away, without manually selecting the active project (auto-selecting workbook project)
- removed deprecated commands from the main menu

IDE fixes
=========
- The IDE was unable to collect log messages from the runtime, now fixed.
- Displaying error message in a dialog in case of exception for all UI commands in QueryStorm (instead of silently failing)

Misc
====
- Fixing Ngen optimization for per-machine installation (requires admin rights). This improves initial startup time for C# scripts and code files.
- Enabled resizing certain tool windows (e.g. log viewer, connect dialog, etc...). This was broken since a recent version that updated the toolwindow style.

IMPORTANT NOTE
===============
Users who have the old version of the QueryStorm Runtime installed will need to manually uninstall it before installing this new version. This is a one-off issue and should not need to be done again in the future. This does not affect users who have the full version installed.

Runtime auto-updater
=================
Until now, runtime users did not get an "Update available" ribbon button when an update is available. This is now fixed so runtime users will get notified and can easily update when a new version is available.

Runtime installer changes
====================
Since the runtime is an XLL addon, it could not be installed per-machine. This version includes a new VSTO addin that acts as a loader for the runtime, effectively allowing the runtime to be installer per-machine.

Additionally, the UpgradeID of the runtime installer has been changed to match the one that the IDE uses. This prevents the user from installing both the Full and the Runtime version (which could cause problems).

New versioning scheme
====================
Moving to a more manageable versioning scheme. Until now, the last two numbers were auto-generated based on the date and time of the release, but these numbers were unwieldy (e.g. 2.9.8581.26987). The new version scheme uses major.minor.build.revision scheme (e.g. 2.10.501.0) as follows:
- Major: this will always remain version 2 (version 3 would be a separate product)
- Minor: increments here usually indicate a break in backward compatibility, meaning that e.g. apps created with v2.7 of the IDE will not run on v2.6 of the runtime. However, some apps might run fine if they don't interact with the changed areas. Also, in this release (2.10.501.0), this number has been incremented from 9 to 10 not because it breaks compatibility with v2.9 (it doesn't) but only because of the versioning schema change (to ensure that this version number is higher than the previous one (2.9.8581.26987).
- Build: this number will be incremented by 1 with each new version. I've chosen 500 as a starting point so this version starts as version 501.
- Revision: this number is currently not used and will likely be skipped or set to 0.

Solving "preview pane" issues in windows explorer
=================================================
When the user has "Preview pane" enabled in the Windows Explorer, an embedded Excel process is created to display the preview. In previous versions of Querystorm, this was causing all sorts of havoc with the QueryStorm runtime. In this version, the runtime is only loaded for actual Excel instances, not for the preview pane and app will work with the correct Excel instance, ignoring the preview pane one.

Other fixes
========
- Additional polishing of WPF dialog windows and fixing dialog centering issues
- Fixing external QueryStorm WPF application (loaded from the dropdown below in the QueryStorm ribbon)

This release includes two important improvements:

1) The Runtime will no longer crash after an Excel file has been opened in the windows explorer's Preview pane. QueryStorm apps will connect to the correct instance of Excel (not the one in the preview pane). This should solve all issues related to the preview pane in windows explorer.

2) All dialogs have been polished and are now consistent across the IDE, runtime, and user apps.

Fixing issues with scripts for defining custom data contexts

Fixing an issue with the QueryStorm Runtime where Excel was crashing when starting apps that register context menu commands, e.g. MondayLink.

Hotfix: VBA API was broken in the last few versions (since 2.9.8553.18963)

Fixing Monday.com data context issues

Hotfix: fixing the "Function Insights" functionality in the code editor

This release fixes several important issues:

- compilation (build) was failing to resolve .NET references on machines that don't have the .NET SDK (installed with Visual Studio)
- Excel would hang for 15s on close whenever a dialog was shown by the IDE, runtime, or an app.
- QueryStorm runtime would not load if a running file explorer instance has started Excel in the preview pane (though there's still an issue with a phantom Excel window showing up if used in the preview pane - to be fixed)
- switching to the latest version of ExcelDNA to fix a bug that was crashing Excel on load when apps that define context menus are used

Breaking change:
=====================================
Due to changes in the runtime/apps contract, the version number has been incremented from v2.8 to v2.9, indicating a breaking change. The runtime now passes its version to apps so they can prompt the user to update the runtime, if necessary. When an app is built with the new version of the IDE, it will not run on older versions of the runtime (if <2.9). However, the app will prompt the runtime user to update the runtime.

List of changes in this version:
================================
- Apps can now specify a minRuntimeVersion
- Added infrastructure for http request for throtting and API key management (request/try/retry loop)
- Improvements in handling licensing prompts (avoid multiple prompts for licensed functions evaluating in multiple cells)
- IDialogServiceExt interface added that allows apps to show dialogs from XAML files and VM objects
- Support for C# scripts returning ExpandoObjects
- Fixed referencing BCL types in the IDE (using ReferenceAssemblies folder instead of GAC)
- IDialogService: all dialogs are show center screen, close on "Esc" key and allow hyperlinks that open the browser
- All licensing dialogs will share remembered username regardless of app
- Syncrhonization context is now assigned inside async Excel functions (so execution after async calls will resume on the main thread)

- Fixing issue with checking license in custom Excel functions in QueryStorm apps
- Minor "publish package" fix
- Minor tweaks to activation UI

Minor patch to licensing UI. Primarily important for new users.

New features
==========
- ability for app developers to license and charge for their apps
- ability for C# scripts to reference other C# scripts

Improvements and bugs fixed
=======================
- The "About" page was not getting disabled even for users with paid licenses
- The table cache was getting updated on each change in Excel, instead of only when the change intersects with a table leading to slow editing of Excel files with large tables
- Improvements in the licensing UI
- Added [view in browser] link in the updater UI
- Fixing StDev function in SQLite

- GPT copilot for SQL scripts added
- About sheet added (can't be removed by community users)
- Minor upgrades for custom Excel functions via C#

See release notes url for details

Bugs fixed:
===========
- editing scripts was impossible after closing and reopening them
- phantom "lib" and "bin" files were appearing in extension projects after build
- failing async functions were crashing Excel instead of returning an error and logging the details
- workbook apps that have settings were bugged in multiple ways
- workbook variables now have a specific type (e.g. "double", "string"... instead of "object")
- sporadic deadlocks were occurring when using the {@some_table} directive
- sporadic deadlocks were occurring when closing workbook apps
- code generation templates for {query} preprocessor directive were broken if more than one parameter was declared
- workbook events were firing before their values were updated via data-binding (e.g. an event handler method might react to a cell change, but the event would get fired before data-bound properties were updated resulting in the event handler using stale data)

Fixes to logic that detects new tables and table changes

=== BREAKING CHANGE (MINOR) ====
This version includes an update to the SQLite engine. Existing workbooks and apps that use SQLite should have their project.config modified.
The following section in the project.config file should be replaced:

"NativeReferences": [
"x86\\SQLite.Interop.QS115.dll",
"x64\\SQLite.Interop.QS115.dll"
],

...with:

"NativeReferences": [
"x86\\SQLite.Interop.QS117.dll",
"x64\\SQLite.Interop.QS117.dll"
],
===============================

Bugs fixed
==========
- several user interface issues (white font on white background in flyouts, text alignment in several places)
- issue when deleting tabular rows
- the code explorer was not detecting external file changes
- Excel functions that accept CallerInfo (e.g. Windy.Query) were broken

Changes
=======
- updated to latest version of SQLite (supports right and full joins)
- updating a ListObject no longer overwrites formula columns

Hotfix
=========
A bug with the data context was preventing loading large tables so workbooks with large tables were not visible to QueryStorm at all.

Changes
=========
SQL scripts that use the {query()} preprocessor directive now generate a Run(...) method that returns a tabular and, optionally (in case there are results in the grid during save), an additional RunWithStronglyTypedResults(...) method that returns the strongly typed results.

The main focus of this release is making sure the QueryStorm installer clears all anti-virus scans. This primarily affects new users, but several additional fixes are also included.

Bugs fixed:
- A phantom file was showing up in the code explorer for SQL scripts that have {query/function/handler} directives, but only in extension (machine-level) projects.
- Resizing the log window in the QueryStorm runtime was freezing the UI.
- The runtime was reporting the wrong version number in the log messages.
- Updated the ExcelDNA library to ensure all antivirus vendors are clearing the QueryStorm runtime installer.

Bugfixes
========
- fixing ngen support i.e. startup performance optimization (for per-machine installations)
- fixing bug with SQLite queries with "OR" expressions in the "WHERE" clause
- switching to a newer version of ExcelDNA that addresses malware false positives

Changes
=======
- copying results from the results grid no longer includes the column headers

New features
==========
- Abiltiy to navigate the caret position history in the editor using Alt+LeftArrow (back) and Alt+RightArrow (forward)

Fixing issue with Microsoft.Extensions.Logging.Abstractions package that was preventing load for apps that define configuration objects

Bugfixes:
===================
- fixes across the board to the integrated debugger
- fixed deadlock when recompiling a project that contains a function that is in use in an open workbook
- fixed writing result as excel table (reapplying filters and inserting into empty table)
- fixed log window in the QueryStorm runtime (it would not start in cases where multiple Excel windows were open once the first one is closed)
- large performance improvements for component that are data bound to workbook tables
- bugfixes and performance improvements in the SQLite engine when working with Excel tables
- various misc bugfixes

Changes:
========
- data contexts now have an event that fires when a variable's data changes
- reorganizing app shortuts and added a template for generating shortcut classes
- code explorer reorganized slightly and several bugs fixed
- updated most 3rd party libraries to latest version
- qs version number can be read from the QueryStorm.Tools assembly and is now logged to the log window

Bug fixes
============
- Added missing 32-bit IDE .exe file (for launching the external IDE app from 32 bit version of Excel)
- SQLite table indexes were not being used in correlated queries, so these queries were slow to run
- SQLite was not handling empty result sets correctly
- The CancellationToken in the ProgressDialog was not working correctly when used inside of a loop

IDE fixes:
- results grid sorting and copy-paste now work again (was broken in previous version)
- significant code editor performance improvements for both C# and SQL code (more responsive while editing large files, faster autocomplete)
- fixed templates for generating code-behind files for SQL scripts for both C# and VB.NET
- significantly improved C# auto-formatting perfomance for large files

Runtime fixes:
- performance issue fixed when writing values cell-by-cell into Excel. Each write was causing the workbook data context to refresh which was causing severe performance problems
- improving overall querying performance of Excel (and other) tables
- resolving a threading issue that caused extension apps to interact with Excel on the wrong (non-UI) thread

IDE:
- various IDE fixes (error line selection, issues with multiple Excel windows open, C# code editor tooltips for generic types fixed)
- overhauling Tabular class (now ITabular interface)
- support for additional data context types: google sheets and monday.com
- basic support for using XAML for defining UI in apps

Runtime & libraries:
- dialogService now has OpenProgressDialog method that displays the progress of an async operation and allows the user to cancel the operation
- async component event handlers can automatically get a progressObserver
- new library for creating "connector" apps that allow "binding" excel tables with external data
- preserving app settings on rebuild but removing them on uninstall
- better error handling when apps fail to load

Fixed bugs (IDE):
====================
- double-clicking an error in a file which was not previously opened would only open the file, not go to the offending line
- C# indentation strategy was not working well with lambdas so reverting to a simpler indentation strategy (for now)
- IDataContext could not be resolved from C# scripts
- importing a workbook project into the workbook was failing to update files properly
- creating a new project after deleting the project with the same name was throwing an exception
- if the default SQLite connection string was deleted in project.config, trying to create a new SQLite script would fail (it now recreates the default connection string)
- the (docked) debugger was running into many issues when debugging code that interacts with the Excel API (was caused by an error in the mechanism that allows the debugger to stay interactive while debugging Excel)

Fixed bugs (runtime):
====================
- installer version number was wrong (1.0 instead of 2.6), which was causing issues with upgrading
- better error logging when data context schema does not match values in a table (e.g. null value found in a non-nullable table column)
- context menu category was visible even if no items inside it were
- IDialogService.ShowWindow() and ShowWindowDialog() methods were not working

Improvements:
====================
- ability to recreate the output table when running SQL scripts. To force the output table to be recreated (overwrites existing columns) add a "!" after the table name, e.g. {@myOutputTable!}

- Introducing C# and VB.NET debugger
- Ability to run QueryStorm IDE as external application
- Improvements to package manager (fixing available updates view)
- Various fixes, improvements, and changes (minor breaking changes - recompiling qs apps is needed)

- Fixing the problem with the default workbook data context that prevented its use (the workaround was creating an explicit data context)
- When using [BindTable] the binder can now detect the table name based on the property type, if it is a table wrapper class (but not if it is Tabular)
- SQL preprocessor now forbids illegal combinations of declarations (e.g. can only use {@tbl} in a handler but not in a function or query) and gives better error information
- Fix encoding issue with .cs files that are created via a code fixer (e.g. extract class into its own file)
- Adding a "netstandard.dll" reference into the default config file as many current NuGet packages rely on it
- Support for configuring SSL in Postgres connection strings

- Hotfix: existing projects that used SQLite fail to load with the new 2.5 version. This hotfix fixes this (check release notes for details)
- Syntax highlighting for the new C# 9 "with" keyword
- Displaying compilation warnings even if build succeeeds

- Upgrading from C#7 to C#9 (support for records, nullable reference types, async streams!)
- Upgrading from SQLite 3.15.2 to 3.36.0 (support for window functions!)
- Easy Excel function results caching
- Several

- Trusted documents (runtime security feature for workbook apps)
- Easier context menus in apps
- Easier settings in apps
- Various bugfixes and improvements

Summary
=======
This version is a collection of bug fixes. There are no breaking changes in this version.

Fixes
=======
- fixed compilation of projects with references to local system dlls
- minor fixes to ribbon class template
- fixed publishing packages with native dlls
- prevent creating multiple projects in a workbook, as this scenario is not yet supported
- better handling for project load errors
- better handling for async function crashes
- fix a focus issue with the undocked QueryStorm window where all text input would go to Excel
- fix for project deletion issues (add error logging, allow deleting projects with readonly files/folders)
- fixed minor ui issues in the undocked ribbon

Apps
======
- Added support for defining ribbons in apps

SQL preprocessor
======
- async functions
- functions that include headers in results
- async event handlers
- queries (for use from .NET code)

Data contexts
======
- complete overhaul of data contexts: switched to C# script for defining data context
- added support for CSV data contexts

Fixes
======
- fixed Excel process crash on exit in certain situations
- fixed Excel process crash on disable runtime Excel Addin
- fixed problem with nesting user defined Excel functions
- fixed activation issue for SQL Pro licenses
- fixed deadlocks in certain situations
- fixed some data handling issues in SQLite
- fixed dozens of IDE issues (logging, code editing, UI glitches)
- fixed handling of special values in user defined functions (error values, missing values)
- fixed installer issue for versions of Excel installed from the windows store
- reorganized confusing connection dialog

Breaking changes
==============
- SQL preprocessor syntax change for commands (event handlers): instead of e.g. {handles eventName} now it's {handler (eventName)}
- new apps will not work on the runtime from previous versions due to a change in the API of the runtime. This change was needed to allow apps to register their own ribbons.
- in projects, data context files will need to be recreated, because the new data context approach has changed

Version 2 is here!