Page last updated
Workflow Engine for .NET Framework
Workflow Engine on the classic CLR, for .NET Framework 4.6.2 and later. The core package targets .NET Standard 2.0, so the same engine, designer, and BPMN importer run in codebases that have not yet moved to .NET 6+.
Add the runtime and a database provider
The packages are the same as on modern .NET. Target framework net462 or later. On .NET Framework, four of the six database providers are available: Oracle needs .NET Core 3.0+, and SQLite needs .NET 6+.
# Package Manager console
PM> Install-Package WorkflowEngine.NETCore-Core -Version 22.1.0
PM> Install-Package WorkflowEngine.NETCore-ProviderForMSSQL -Version 22.1.0
# or the dotnet CLI
dotnet add package WorkflowEngine.NETCore-Core --version 22.1.0| Database | NuGet package | Version | Runs on |
|---|---|---|---|
| SQL Server, Azure SQL | WorkflowEngine.NETCore-ProviderForMSSQL | v22.1.0 | .NET Framework 4.6.2+ and all modern .NET |
| PostgreSQL | WorkflowEngine.NETCore-ProviderForPostgreSQL | v22.1.0 | .NET Framework 4.6.2+ and all modern .NET |
| MySQL | WorkflowEngine.NETCore-ProviderForMySQL | v22.1.0 | .NET Framework 4.6.2+ and all modern .NET |
| MongoDB, Azure Cosmos DB | WorkflowEngine.NETCore-ProviderForMongoDB | v22.1.0 | .NET Framework 4.6.2+ and all modern .NET |
| Oracle | WorkflowEngine.NETCore-ProviderForOracle | v22.1.0 | Not on .NET Framework. .NET Core 3.0 and later only. |
| SQLite | WorkflowEngine.NETCore-ProviderForSQLite | v22.1.0 | Not on .NET Framework. .NET 8 and later only. |
Designer packages for your front end
Workflow Designer runs in the browser, so the npm packages are the same on either runtime. Vue and any plain page use the vanilla package, shown with a running sample on the JavaScript workflow designer page; React renders the wrapper component, shown with a running sample on the React workflow designer page; Blazor embeds the designer through IJSRuntime interop, shown file by file on the Blazor workflow designer page. Every framework path is covered on the workflow designer page.
Should I use this build or the .NET 6+ build?
Stay on this page only if your host application cannot move to .NET 6 or later. The API surface is identical on both runtimes, so a future migration is a runtime change, not a rewrite. For a new project, pick modern .NET: it gets new framework features first and all six database providers.
Licensing
Workflow Engine Free costs nothing and carries documented usage limits. Workflow Engine and Workflow Engine NEO ship as perpetual licenses per software product: one-time fee, no royalties, no per-execution charges.
From install to a running workflow
Three steps take you from an empty project to an evaluated engine. Each step links the guide that walks you through it.
01Integrate
Wire the runtime into your app
Register the runtime, connect your database, and start a first process. The integration guide covers every step with working C#.
02Explore
Model a scheme in the designer
Embed Workflow Designer, build an approval flow, and browse the documentation for schemes, commands, timers, and plugins.
03Evaluate
Request a trial key
Workflow Engine Free has usage limits. A trial key grants temporary access to the licensed product and edition you are evaluating.