Does the .NET edition use Java-style getters?
No. GSP .NET exposes idiomatic C# properties: parser.Errormessage, stmt.ResultColumnList, table.FullName, table.AliasName. If you are porting code or examples written against the Java edition, getFromClause() becomes .FromClause and getAliasName() becomes .AliasName — the Java method forms do not exist in the .NET assembly.
Which SQL dialects does the .NET edition support?
15 dedicated grammars: Oracle, SQL Server (T-SQL), MySQL, PostgreSQL, DB2, Teradata, Snowflake, Redshift, Hive, Impala, Netezza, Greenplum, Informix, Sybase ASE, MDX. ANSI, generic, ODBC, Access, and Firebird are handled by the shared core grammar. BigQuery, SAP HANA, and DAX are available in the Java edition only — constructing a .NET parser for those vendors throws NotSupportedException rather than silently mis-parsing.
Can I ship a build with only the databases I license?
Yes. Each dialect is a compile-time switch (/p:includeOracle=true, /p:includeMssql=true, and so on), so a per-customer build carries only the grammar tables you paid for and nothing else. This keeps the shipped assembly small and the licensed surface explicit.
Does validating SQL require a database connection?
No. Parsing, validation, formatting, and lineage all run entirely in-process with no server, driver, or credentials. This is what makes GSP usable inside air-gapped and regulated environments.
Is the .NET edition on nuget.org?
The public nuget.org listing for gudusoft.gsqlparser trails the current release. GSP .NET 4.1.0.6 (released 2026-07-15) is supplied directly by Gudu with your evaluation or licence, so you can restore it from an internal feed or a local package folder.