DotNetDBTools.CodeParsing
0.3.1
See the version list below for details.
dotnet add package DotNetDBTools.CodeParsing --version 0.3.1
NuGet\Install-Package DotNetDBTools.CodeParsing -Version 0.3.1
<PackageReference Include="DotNetDBTools.CodeParsing" Version="0.3.1" />
paket add DotNetDBTools.CodeParsing --version 0.3.1
#r "nuget: DotNetDBTools.CodeParsing, 0.3.1"
// Install DotNetDBTools.CodeParsing as a Cake Addin #addin nuget:?package=DotNetDBTools.CodeParsing&version=0.3.1 // Install DotNetDBTools.CodeParsing as a Cake Tool #tool nuget:?package=DotNetDBTools.CodeParsing&version=0.3.1
DotNetDBTools is a set of libraries to define, analyze and deploy (publish migrate) relational databases throughout their evolution using database as code approach.
Or in other words - state-based (declarative) database version control tools.
It provides the means to conviniently describe database objects for the supported DBMS as c# code or as sql in a declarative way, to analyze it and the means of publishing it to the selected DBMS with automatic differences calculation between what's being published and what's currently in the DBMS now.
Agnostic definition for standard sql objects (Tables, Views, Indexes, Triggers) is also supported (as c# code only) and can then be used to publish to any supported DBMS.
DotNetDBTools.CodeParsing is a library mainly for internal use by other DotNetDBTools.* packages, but may also contain helpful functionality to be used directly.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Antlr4.Runtime.Standard (>= 4.9.3)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on DotNetDBTools.CodeParsing:
Package | Downloads |
---|---|
DotNetDBTools.Analysis
DotNetDBTools is a set of libraries to define, analyze and deploy (publish migrate) relational databases throughout their evolution using database as code approach. Or in other words - state-based (declarative) database version control tools. It provides the means to conviniently describe database objects for the supported DBMS as c# code or as sql in a declarative way, to analyze it and the means of publishing it to the selected DBMS with automatic differences calculation between what's being published and what's currently in the DBMS now. Agnostic definition for standard sql objects (Tables, Views, Indexes, Triggers) is also supported (as c# code only) and can then be used to publish to any supported DBMS. DotNetDBTools.Analysis is a library mainly for internal use by other DotNetDBTools.* packages, but may also contain helpful functionality to be used directly. |
GitHub repositories
This package is not used by any popular GitHub repositories.