According to this link (which is written for older ASP.NET), "It is not necessary for ASP.NET Core, because application is exposed by a console application that it already always on." Could there be another reason for the problems we are having?
Do you have a link as to how that can be done in Core?
Hi,
We have just one Hangfire job running on our website, running every hour on the hour. For some reason it has stopped running and I cannot reproduce the problem in development.
In the logs I see the following: DEBUG 2019-05-11 14:16:47,841 [88 ] Abp.Modules.AbpModuleManager - Shutting down has been started DEBUG 2019-05-11 14:16:47,843 [88 ] bp.Hangfire.HangfireBackgroundJobManager - Stop background worker: Abp.Hangfire.HangfireBackgroundJobManager DEBUG 2019-05-11 14:16:47,844 [88 ] bp.Hangfire.HangfireBackgroundJobManager - WaitToStop background worker: Abp.Hangfire.HangfireBackgroundJobManager DEBUG 2019-05-11 14:16:47,844 [88 ] Abp.Modules.AbpModuleManager - Shutting down completed. INFO 2019-05-11 14:16:47,873 [88 ] Hangfire.BackgroundJobServer - Hangfire Server stopped.
Thanks. I'm unclear how I would incorporate this with a call of the following form (which automatically unblocks the page when the promise is completed):
abp.ui.setBusy(
$('#MyLoginForm'),
abp.ajax({ ... })
);
I am trying to use abp.ui.setBusy as per below but cannot get the spinner to work:
abp.ui.setBusy(
$('#MyLoginForm'),
abp.ajax({ ... })
);
In the documentation I read the following: "The UI Busy API is implemented using spin.js. To make it work, you must include its JavaScript file, then include abp.spin.js to your page (See this JavaScript file for the simple implementation and defaults)."
Unfortunately there is no link provided to the JavaScript example file. Can anyone help please?