dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated to use inline-note 

Signed-off-by: Whit Waldo <whit.waldo@innovian.net>
This commit is contained in:
Whit Waldo 2025-01-23 12:01:19 -06:00
parent 9c67567228
commit 7f6daad698
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
daprdocs/content/en/developing-applications/building-blocks/jobs/howto-schedule-and-handle-triggered-jobs.md
View File

@ -39,15 +39,16 @@ is available when the job is triggered in the future:
- The database name (`DBName`) - The database name (`DBName`)
- The database location (`BackupLocation`) - The database location (`BackupLocation`)
Create an ASP.NET Core project and add the latest version of `Dapr.Jobs` from NuGet. While it's not strictly necessary Create an ASP.NET Core project and add the latest version of `Dapr.Jobs` from NuGet.
> **Note:** While it's not strictly necessary
for your project to use the `Microsoft.NET.Sdk.Web` SDK to create jobs, as of the time this documentation is authored, for your project to use the `Microsoft.NET.Sdk.Web` SDK to create jobs, as of the time this documentation is authored,
only the service that schedules a job will receive trigger invocations for it. As those invocations expect an endpoint only the service that schedules a job will receive trigger invocations for it. As those invocations expect an endpoint
that can handle the job trigger and requires the `Microsoft.NET.Sdk.Web` SDK, it's recommended that you that can handle the job trigger and requires the `Microsoft.NET.Sdk.Web` SDK, it's recommended that you
use an ASP.NET Core project for this purpose. use an ASP.NET Core project for this purpose.
Start by defining types to Start by defining types to persist our backup job data and apply our own JSON property name attributes to the properties
persist our backup job data and apply our own JSON property name attributes to the properties so they're consistent so they're consistent with other language examples.
with other language examples.
```cs ```cs
//Define the types that we'll represent the job data with //Define the types that we'll represent the job data with