I tried, but when I disable it from appsettings I get this error:
Volo.Abp.AbpInitializationException: An error occurred during the initialize Volo.Abp.Modularity.OnPreApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.BackgroundWorkers.Hangfire.AbpBackgroundWorkersHangfireModule, Volo.Abp.BackgroundWorkers.Hangfire, Version=8.3.2.0, Culture=neutral, PublicKeyToken=null: An exception was thrown while activating ?:Volo.Abp.Hangfire.AbpHangfireBackgroundJobServer -> ?:Hangfire.JobStorage.. See the inner exception for details.
---> Autofac.Core.DependencyResolutionException: An exception was thrown while activating ?:Volo.Abp.Hangfire.AbpHangfireBackgroundJobServer -> ?:Hangfire.JobStorage.
---> System.InvalidOperationException: Current JobStorage instance has not been initialized yet. You must set it before using Hangfire Client or Server API. For .NET Core applications please call the IServiceCollection.AddHangfire extension method from Hangfire.NetCore or Hangfire.AspNetCore package depending on your application type when configuring the services and ensure service-based APIs are used instead of static ones, like IBackgroundJobClient instead of BackgroundJob and IRecurringJobManager instead of RecurringJob.
at Hangfire.JobStorage.get_Current() in C:\projects\hangfire-525\src\Hangfire.Core\JobStorage.cs:line 42
Hi @maliming, sorry to ask, but can you explain what these options do? I'm always interested in understanding ABP services, since I don't use many of them, and I'd also like to find a way to disable anything I don't need to improve debugging and development.
Thanks
Sorry, I don't have time to test the proposed solution yet. Could you check if it works in the project already shared? If not, I'll do it tomorrow. In the meantime, I'll keep the ticket open.
Thanks
Ok, thanks anyway for your support
I looked at the PR and it seems to work. I'm still having issues with hot reloading, but I think it's due to factors outside of the ABP.
Do you have any suggestions on how to make debugging more efficient?
Thanks
I will try, however my first problem is that I can't use the application settings to register Hangfire or not.
Thanks
I created the private GitHub repository and sent you the invitation.
Thanks
Yes, for this ticket.
Thanks.
As written in previous posts, I also hypothesized that it could depend on the number of entities, but this is because with each modification it must recompile the entire project and not just the individual modified files.
Can you try again by modifying some razor.cs code and also running the api in debug?
Reproduce step:
bool test = true;After a lot of minutes I get an error.
I need to develop using debugging simultaneously on both projects (API + Blazor). I can't reduce my components because my application must handle all those entities.
As the title says: "How can I have just a standalone Blazor Web Assembly project?" Is it possible to have just the Blazor.Client project and launch it as a standalone project?
This should solve my slowness problems.
Thanks
But how do I register Hangifire only in the version to be released on ETL Server?
I tried creating a JobManagerModule that derives from AbpModule in which I try to register Hangfire based on the app settings, but it seems like it always needs to be registered in the application servers as well.
Example of my code:
Thanks
P.S. I sent you the solution.