After updating my Blazor solution to Xpand.XAF.All 4.242.4 and .NET 9.0, the Hangfire jobs stopped working

[ricardoamm]

The Trigger and Pause buttons in the Job Detail view do nothing.

[apobekiaris]

did you tried the minor from #1083 my guess is it relates

[ricardoamm]

The problem remains.
I update the Hangfire Version, and now i'm getting:

System.TypeLoadException: 'Could not load type 'Hangfire.HangfireServiceCollectionExtensions' from assembly 'Hangfire.AspNetCore, Version=1.8.17.0, Culture=neutral, PublicKeyToken=null'.'

[apobekiaris]

please provide a sample

[ricardoamm]

Seems to be any problem with JobSchedulerService in the :

internal static IObservable Connect(this ApplicationModulesManager manager)
=> Observable.If(() => DesignerOnlyCalculator.IsRunTime,manager.Defer(() => manager.CheckBlazor(typeof(HangfireStartup).FullName, typeof(JobSchedulerModule).Namespace)))
.Merge(manager.WhenApplication(application => application.ScheduleJobs().Merge(application.DeleteJobs())
//.MergeToUnit(application.RefreshDetailViewWhenObjectCommitted(typeof(Job)))
//.MergeToUnit(application.RefreshListViewWhenObjectCommitted())
)
.Merge(manager.TriggerJobsFromAction())
.Merge(manager.PauseJobsFromAction())
.Merge(manager.ResumeJobsFromAction())
.Merge(manager.JobDashboard())
);

Because the JobsFromActions are not executed when the buttons are clicked

[apobekiaris]

yeah switching .net frameworks might seem easy but the devil is hidden there. Unfortunately I have been travelling not much time to research yet

[ricardoamm]

thanks, i will wait.
i'm stuck

[ricardoamm]

if possible, please update Hangfire dependency to Version_180

[apobekiaris]

no idea what is happening with your solution neither I could run it my self. I create a new install everything as prompted used the inmem hangfire storage so jobs do not persist in each app run. Added a job and noticed executing when I Trigger actions

DXApplication1.zip

[ricardoamm]

I compiled and ran your example and got exactly the same behavior.

[apobekiaris]

what do u mean I put a breakpoint at the Failed moethod and was hitted

[JobProvider]
        public void Failed() {
            throw new NotImplementedException();
        }

[ricardoamm]

Here goes de recording

recoprding.zip

[apobekiaris]

this must be a new Xaf Job object created just before you trigger the job right?

[ricardoamm]

yes

[ricardoamm]

I have a production portal where sometimes I have to trigger jobs manually. When can I expect a solution?

[apobekiaris]

I do not see how to repro your problem, my app works fine on my side and not in yours, what to say try to find alternatives e.g. maybe another machine cause I can trigger jobs manually just fine as per my video

[ricardoamm]

Which video?

[apobekiaris]

I guess I missed to press Comment and never post my answer b4. I attach it again, using it and follow all the steps in the video you should also get stopped in the breakpoint.

[apobekiaris]

chrome_emJIcFFKjd.mp4

[apobekiaris]

u can manually try to trigger the job from your own code this is Hangfire api and nothing to do with Xaf.

does that work?

[ricardoamm]

Yes, manually through the code, I can't trigger the job.
I tried running your sample again, and the NuGet package Xpand.Xaf.Modules.JobScheduler.Hangfire version 2.424.4.3 you're using doesn't exist. Only version 4.242.4 is available. Are there any differences?

[apobekiaris]

use the latest version does not matter I changed nothing

[ricardoamm]

The problem isn't related to Hangfire. it's related to the SimpleAction (Pause, Resume, Trigger, ...) in the JobSchedulerService, which are not executed when the buttons are clicked. They are subscribed but never executed.

Could you try with NuGet 4.242.4 to replicate the exact references I'm using?

[apobekiaris]

That's why I suspected #1083 but my tests show it works

[ricardoamm]

What can I do in the meantime?

[apobekiaris]

try 4.242.4.2 is the latest lab which for sure included #1083

[ricardoamm]

Its working, thanks.
I compiled the module jobscheduler with hangfire 1.8 and its Running well.