Hangfire.AspNetCore doesn't work with .Net 10 when Newtonsoft.Json is referenced using PrivateAssets="All"

[DaveNatalieTripArc]

In a class library, I have Newtonsoft.Json and Hangfire.AspNetCore referenced using the following package references.

<PackageReference Include="Hangfire.AspNetCore" Version="1.8.22" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.4" PrivateAssets="All" />

This worked in .Net 9, but after targeting .Net 10, I now get the following runtime exception.

System.IO.FileNotFoundException: 'Could not load file or assembly 'Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. The system cannot find the file specified.'

If I remove PrivateAssets="All" from the package reference, everything works, but this will mean that anyone who references my library will now have visibility to Newtonsoft.Json. My goal is to only use Newtonsoft with Hangfire out of necessity, but effectively "hide" it from the rest of the application.

Here is the full Stack Trace for the Exception.

   at Hangfire.GlobalConfigurationExtensions.UseRecommendedSerializerSettings(IGlobalConfiguration configuration, Action`1 settingsConfiguration)
   at Hangfire.GlobalConfigurationExtensions.UseRecommendedSerializerSettings(IGlobalConfiguration configuration, Action`1 settingsConfiguration)
   at Hangfire.GlobalConfigurationExtensions.UseRecommendedSerializerSettings(IGlobalConfiguration configuration)
   at [redacted]
   at Hangfire.HangfireServiceCollectionExtensions.<>c__DisplayClass0_0.<AddHangfire>b__0(IServiceProvider provider, IGlobalConfiguration config)
   at Hangfire.HangfireServiceCollectionExtensions.<>c__DisplayClass1_0.<AddHangfire>b__14(IServiceProvider serviceProvider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(ServiceIdentifier serviceIdentifier)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
   at Hangfire.HangfireServiceCollectionExtensions.ThrowIfNotConfigured(IServiceProvider serviceProvider)
   at Hangfire.HangfireApplicationBuilderExtensions.UseHangfireDashboard(IApplicationBuilder app, String pathMatch, DashboardOptions options, JobStorage storage)
   at [redacted]

[sabiland]

FYI, I have upgraded today our company project to DotNet10 -> And I do not see any issues with Hangfire 1.8.22

[odinserj]

I believe this is due to this breaking change in .NET 10 – https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/prune-packagereference-privateassets, so it's possible to revert the behavior to the old one. However, I wouldn't hide Newtonsoft.Json from public, because it is not a private dependency, which is required only for Hangfire, it is an application-wide dependency, and application code have influence on serialization of types used as background job arguments. So, Newtonsoft.Json is a requirement for an application to have to make Hangfire work.

[supergibbs]

All the more reason to migrate to System.Text.Json

#2202
#2033
#2305

[odinserj]

Migration to System.Text.Json is very difficult, guys. I have attempted to make it multiple times, and only this year I found an acceptable solution to cover cases like serialization attribute usage. It's easy to make another version of Hangfire, which works with System.Text.Json from scratch, but it's very difficult to make a transition so nothing is broken.

However, migration to System.Text.Json will not help in solving the problem of this issue. Only abstraction above both of them will solve this.