MicroWorkflow.AdoMsSql
1.3.4
There is a newer version of this package available.
See the version list below for details.
See the version list below for details.
dotnet add package MicroWorkflow.AdoMsSql --version 1.3.4
NuGet\Install-Package MicroWorkflow.AdoMsSql -Version 1.3.4
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="MicroWorkflow.AdoMsSql" Version="1.3.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add MicroWorkflow.AdoMsSql --version 1.3.4
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: MicroWorkflow.AdoMsSql, 1.3.4"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install MicroWorkflow.AdoMsSql as a Cake Addin #addin nuget:?package=MicroWorkflow.AdoMsSql&version=1.3.4 // Install MicroWorkflow.AdoMsSql as a Cake Tool #tool nuget:?package=MicroWorkflow.AdoMsSql&version=1.3.4
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
Microsoft SQL Server
This package provides integration with Microsoft SQL server to persist steps in the database.
Getting started
To get started
- Create database scemas and tables with https://github.com/kbilsted/MicroWorkflow.net/blob/master/src/MicroWorkFlow.AdoPersistence/createdb.sql
- Optionally you rename the schemas and tables to whatever you see fit. Then, on an instance of
SqlServerPersisterset the valuesTableNameReady,TableNameFail,TableNameDone. - Register in your IOC container
SqlServerPersistersuch that a new instance is created when the type is resolved. This is due to the fact that each instance controls its local transaction.
var logger = new DiagnosticsStepLogger();
builder.Register<IStepPersister>(c => new SqlServerPersister(ConnectionString, logger));
Due to the support of renaming, you can spin up multiple workflow engines within the same solution. This is useful when you want to create queues with different priorities, for example, a "high priority queue" and a "low priority queue".
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. 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 is compatible. 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. |
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
-
net6.0
- Microsoft.Data.SqlClient (>= 5.1.5)
- MicroWorkflow (>= 1.3.4)
-
net8.0
- Microsoft.Data.SqlClient (>= 5.1.5)
- MicroWorkflow (>= 1.3.4)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.