Conversation
| @@ -1,6 +1,8 @@ | |||
| namespace SignalRApp | |||
|
|
|||
| #if !NET6_0 | |||
There was a problem hiding this comment.
#if !NET6_0_OR_GREATER
The same problem in 2 other places.
|
I think this should be changed to 2022. The 2019 image on Appveyor does not have .NET 6 and you'd need to install it manually. Line 3 in dab3b00 |
|
Hello, @Shmew, are you around? This would be cool to have. Trying to add I actually wonder if it's really necessary to pin versions of those official .NET packages. |
|
@Shmew what's preventing this from being merged? Anything we can help with? |
|
@PierreYvesR thanks for getting this across the line! I noticed in the |
- Add Fable 4.0.0-theta-018 dotnet tool. - Add separate Paket dependency groups for Fable demo and tests with Fable.Core 4.0.0-theta-007 and Fable.Elmish 4. - Update Fable.SignalR.Tests to Elmish 4. - Update SignalR NPM-package version range (for Femto). - Update webpack.config.json and package.json (to use Fable 3+ as dotnet tool). - Add Pnpm for JS package management (could be switched back to Yarn by a couple little build-script changes). - gitignore and editorconfig updates.
…unctions (`StreamFrom`).
…ad of internal) -- to fix the hub registration error in DI-container; and some code reformatting.
…sion method Previously all the `OnConnected`, `OnDisconnected`, `Both` hubs have been registered as the `Both` hub specified in the wildcard-case in `Config` match.
Merging ArtemyB's changes
Pull request checklist
Please check if your PR fulfills the following requirements:
fake buildor.\build.cmd) on local branch was successfulbuild -t NuGetworksPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Doesn't support .Net 6.
What is the new behavior?
Supports .Net 6
Does this introduce a breaking change?
Other information