SqlOrchestrationService is not visible when referencing Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer about durabletask-mssql HOT 1 OPEN

Hi @mikegoatly. The reason you're not seeing the DurableTask types anymore is because Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer doesn't have a direct dependency on the DurableTask assemblies. In fact, it doesn't define any types at all, which it seems you already noticed. Think of the "Worker" nuget packages as proxies telling what the Functions host needs to load without putting any dependencies into your actual app code.

To get your scenario working again, you should add a reference to Microsoft.DurableTask.SqlServer directly (not the AzureFunctions version, but that might still work).

I'm seeing minor differences in the schemas generated between the two

Ah, looks like this is a bug is the Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer package because it's referencing an older version of the Microsoft.DurableTask.SqlServer.Functions dependency (here).

The safe thing for you to do in this case is to specifically reference the latest v1.1.x release (not the v1.2.x release) of Microsoft.DurableTask.SqlServer in your project. This will ensure that both the runtime and your custom migration logic are using the same schema version. It may not be strictly necessary since the 1.2.0 schema should be backwards compatible with the 1.1.x schema, but it might be a good idea just to be safe.

I'll need to publish a fix to Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer to reference the 1.2.x version of Microsoft.DurableTask.SqlServer.Functions. Moving forward, for your migration code, make sure to keep these two version numbers in sync. Once this bug is fixed, that will ensure that you're always using the correct database schema.

from durabletask-mssql.