Hangfire.AspNet | Recommended way to install Hangfire | Frontend Framework library

Here's the FetchData component that uses a standard Timer.

A few points:

1. I've added a Task.Delay in to emulate a slow connection and to show that the page is refreshing.
2. StateHasChanged is wrapped like this await this.InvokeAsync(StateHasChanged) to ensure it gets run on the UI context thread.
3. Implements IDisposable as we have the Timer event handler to disconnect.

I got it working like this:

Okay, so here's what I did wrong that resulted in me getting "ghost" servers in Hangfire. Basically, I had two instances of my application running and I didn't even realize it. I had deployed my application to our TEST server in Azure which was using an Azure Database. This test app was also set to "always run". Now, when I was testing my changes to the application in my development machine I was also connecting to the same Azure database that the test application was connected to. This is why, even when I truncated the Hangfire tables, the "ghost" servers kept coming back. These servers belonged to the application that was running on the TEST server, and since the application was always running, the servers kept getting recreated, and the old code on the TEST server kept being executed since I had never deployed the changes from my DEV server to the TEST server on Azure.

Basically, it was my own stupid fault.

there could be two issues

1. missing SDK, you can check SDK version using

"I have one Server project" is a little unclear since we can only see . I assume you want ot convert form a Blazor Server App to a WebAssembly app?

The project type is now WebAssembly but you are including, amongst others,

You can't access a database from a browser app directly. It's not supported and it wouldn't be safe (all clients would have access to the connection string).

This project needs to be split into a Client and a Server (API) part.

Your best course is to create a project (in a temp folder) from the full Blazor Wasm + Asp.Net Hosted + Individual Accounts template. It'll give you a complete reference for what goes where.

First off, the important part of the exception you are seeing is:

Unable to resolve service for type 'Wms.Alarming.AlarmingConfig' while attempting to activate 'Wms.Alarming.AlarmingService'

Which indicates that somewhere in your code (a part you haven't shown yet) you are trying to inject an instance of AlarmingService.

You've configured how to resolve a singleton service for the interface IAlarmingService, which means you should be able to have a class depend on IAlarmingService. However, if your class depends specfically on AlarmingService (not the interface), you will get this error, because you have not defined how to resolve a dependency of type AlarmingService.

Either...

• the code you haven't shown should only depend on IAlarmingService and not the concrete class itself (AlarmingService) or..
• you need to also configure DI container to handle a dependency specifically of type AlarmingService, e.g.:

I am not sure the DI in Hangfire is for this purpose.

You need dependency injection to resolve inner dependencies, not to resolve the main type you want to use.

You can check the documentation here.

Check this answer with same problem.