nulltoken
nulltoken
>just wanted to know if this was done for a reason? paging @poveden that may have a better view on this
> We would like to start using merged changes. What is the release process? This was released as part of v7.2.0 (72c5b67e3604d230637d13098ecb725190e14385)
Deploy the fluent builder interface to dynamic jobs Related https://github.com/NCronJob-Dev/NCronJob/issues/221#issuecomment-2712836821
If you prefer CorrelationId over OrchestrationId (from a naming standpoint), let's close this issue. I don't see any value in having both exposed.
>Now if there are other reasons for the UseNCronJob() like pipeline ordering etc. then that's perfectly fine There are indeed other reasons :wink: It's not a matter of code style....
>If the order of the registrations of NCronJob is determined by where the UseNCronJob() appears That part is unclear to me. To what "order" are you referring to? > It'll...
>I think my overall conclusion would be to remove the ability of calling AddNCronJob multiple times. That would make things much simpler :wink: Provided this happens, and we rewire the...
>The only downside with this: Imagine you have a startup job that does DB seeding or migrations. As .NET offers to start jobs in parallel, other background services that use...
> > I think my overall conclusion would be to remove the ability of calling AddNCronJob multiple times. > > That would make things much simpler 😉 > > Provided...
>it might break folks that have multiple registrations.