DurableFunctionsMonitor.DotNetIsolated.MsSql 6.7.0

Requires NuGet 2.5 or higher.

dotnet add package DurableFunctionsMonitor.DotNetIsolated.MsSql --version 6.7.0
                    
NuGet\Install-Package DurableFunctionsMonitor.DotNetIsolated.MsSql -Version 6.7.0
                    
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="DurableFunctionsMonitor.DotNetIsolated.MsSql" Version="6.7.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="DurableFunctionsMonitor.DotNetIsolated.MsSql" Version="6.7.0" />
                    
Directory.Packages.props
<PackageReference Include="DurableFunctionsMonitor.DotNetIsolated.MsSql" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add DurableFunctionsMonitor.DotNetIsolated.MsSql --version 6.7.0
                    
#r "nuget: DurableFunctionsMonitor.DotNetIsolated.MsSql, 6.7.0"
                    
#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.
#addin nuget:?package=DurableFunctionsMonitor.DotNetIsolated.MsSql&version=6.7.0
                    
Install DurableFunctionsMonitor.DotNetIsolated.MsSql as a Cake Addin
#tool nuget:?package=DurableFunctionsMonitor.DotNetIsolated.MsSql&version=6.7.0
                    
Install DurableFunctionsMonitor.DotNetIsolated.MsSql as a Cake Tool

DurableFunctionsMonitor.DotNetIsolated.MsSql

An incarnation of DurableFunctionsMonitor that can be "injected" into your .NET Isolated Azure Function, that uses Durable Task SQL Provider.

How to use

  • Install from NuGet:

    dotnet add package DurableFunctionsMonitor.DotNetIsolated.MsSql
    
  • Initialize by calling .UseDurableFunctionsMonitorWithMsSqlDurability() extension method during your Function's startup, like this:

    var host = new HostBuilder()
        .ConfigureFunctionsWorkerDefaults((hostBuilderContext, workerAppBuilder) => {
    
            workerAppBuilder.UseDurableFunctionsMonitorWithMsSqlDurability();
    
        })
        .Build();
    

    By default all settings are read from env variables (all the same config settings are supported), but those can be programmatically (re)configured like this:

    var host = new HostBuilder()
         .ConfigureFunctionsWorkerDefaults((hostBuilderContext, workerAppBuilder) => {
    
             workerAppBuilder.UseDurableFunctionsMonitorWithMsSqlDurability((settings) => 
             {
                 // Override DfMon's settings here, e.g.
                 settings.Mode = DfmMode.ReadOnly;
                 // ....
             });
    
         })
         .Build();
    

    By default DfMon's endpoint will appear at http://localhost:7071/my-api-route-prefix/durable-functions-monitor. To override that behavior (e.g. to have it served from the root) add a custom statics-serving function like this:

    namespace DurableFunctionsMonitor.DotNetIsolated
    {
         public class MyCustomDfMonEndpoint: ServeStatics
         {
             public MyCustomDfMonEndpoint(DfmSettings dfmSettings, DfmExtensionPoints extensionPoints, ILoggerFactory loggerFactory) : 
                 base(dfmSettings, extensionPoints, loggerFactory)
             {
             }
    
             [Function(nameof(MyCustomDfMonEndpoint))]
             public Task<HttpResponseData> ServeDfMonStatics(
                 [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = "/{p1?}/{p2?}/{p3?}")] HttpRequestData req,
                 string p1,
                 string p2,
                 string p3
             )
             {
                 return this.DfmServeStaticsFunction(req, p1, p2, p3);
             }
         }
    }
    
Product 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 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.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp2.1 is compatible.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
6.7.0 256 5/14/2025
6.7.0-beta2 218 5/13/2025
6.7.0-beta1 237 5/12/2025
6.6.0-beta4 139 2/6/2025
6.6.0-beta3 149 2/6/2025
6.6.0-beta2 145 2/6/2025
6.6.0-beta1 129 2/6/2025