Base solution for your next web application

Activities of "borisproceptio"

The problem was that multiple instances were running in the same database. We added Hangfire server with specific SchemaName and it solved the issue. This article describes the same issue.

Prerequisites

Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • What is your product version? v11.0.0
  • What is your product type (Angular or MVC)? MVC
  • What is product framework type (.net framework or .net core)? .NET CORE 6

Hi guys,

recently I've updated the app from .NET Core 5 to the latest version. With that I've also updated the Hangfire package. After that I am getting the following error in production:

As a part of migrating to new version of ASPNETZERO the signature of the ExecuteAsync method of the background job had to be changed from protected to public. Implementation of the background job look like this:

And I am calling the background job like this:

This are the packages I am using:

So basically the only thing that has changed was the method signature and after that I am getting the error that I pasted above. Any help would be much appreciated.

Thanks.

Question

Prerequisites

Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • What is your product version? v10.2.0
  • What is your product type (Angular or MVC)? MVC
  • What is product framework type (.net framework or .net core)? .NET Core

Hi,

I am having issues with hot reload feature. When I update .xaml nothing happens in emulator. I've checked the VS settings and everything seems normal and hot reload works with blank Xamarin Forms projects. Is this behaviour expected?

Thanks.

Showing 1 to 3 of 3 entries