mirror of https://github.com/dapr/dotnet-sdk.git
89d9d56bd5
fix: Point-in-time not getting scheduled, job payload not being property set on job invocation When setting a single point-in-time job, the SDK was incorrectly assigning it as a schedule which would promptly fail cron validation. Rather, this now properly sets it to `dueTime` instead. Further, when a Job is invoked, only the payload it was registered with is provided in the callback, not all the elements of a Get Job response, so this was modified to return the `ReadOnlyMemory<byte>` originally provided in the payload back to the caller. Reviewed by: @philliphoff Refs: #1455 #1457 |
||
|---|---|---|
| .. | ||
| AI/ConversationalAI | ||
| Actor | ||
| AspNetCore | ||
| Client | ||
| GeneratedActor | ||
| Jobs/JobsSample | ||
| Workflow | ||
| .editorconfig | ||
| Directory.Build.props | ||
| README.md | ||
README.md
Dapr .NET Core examples
This repository contains a samples that highlight the Dapr .NET SDK capabilities:
| Sample | Description |
|---|---|
| 1. Client | The client example shows how to make Dapr calls to publish events, save state, get state and delete state using a Dapr client. |
| 2. Actor | Demonstrates creating virtual actors that encapsulate code and state. |
| 3. ASP.NET Core | Demonstrates ASP.NET Core integration with Dapr by creating Controllers and Routes. |
| 4. Workflow | Demonstrates creating durable, long-running Dapr workflows using code. |