[BUG] Can't add OrgnalR Nuget package to Service Fabric service (stateless, ASP.NET Core web application) about orgnalr HOT 4 CLOSED

Hey @danvanderboom So I ended up getting it going in the end. Version 1.4.1 installs correctly for my application.

I'm gonna close this one out, feel free to reopen if it continues to fail for you 👍

from orgnalr.

Thanks for the bug report @danvanderboom. Very interesting. I'll have a dig tonight to see what the issue is. Hopefully can push out a version that's compatible

from orgnalr.

I am able to reproduce... This isn't the first time I've run into issues with this System.Text.Encoding package (not in OrgnalR but professionally). Will keep you in the loop

from orgnalr.

So. I thought it might be that I should be targeting netcoreapp3.1 and netstandard2.0, however this did not solve the issue.

I then went and installed Microsoft.AspNetCore.SignalR.Core - Worked
Installed Microsoft.Orleans.Runtime.Abstractions - Failed

Tried both combinations. So it seems like an issue when Microsoft.ServiceFabric.AspNetCore.Kestrel is installed with BOTH of those packages.

To be honest, I think the Microsoft.AspNetCore.SignalR.Core package is overdue for an update (if only to fix issues like this). It hasn't been updated since 2018. I'm gonna try and deploy a version which fixes the conflicts, but I have a feeling it won't be solvable in OrgnalR, and in your application you will need to go through and install each conflicting package explicitly

from orgnalr.