-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to .NET Core 3.0-preview6 #59
Comments
I can confirm that for me preview 6 failed, but preview 5 works great so far. The hot reload is amazing! |
This depends on the Blazor SignalR extension to be updated for preview6, see BlazorExtensions/SignalR#32. |
It's still broken. I guess it hasn't been deployed yet? If so, maybe we should not close an issue until the solution has been deployed? How could I check the Blazor version that is installed? Thanks |
It is merged to master, which is why I closed the issue. You can try the nightly build by adding the CI to your NuGet sources: https://ci.appveyor.com/nuget/bolero |
@Tarmil Thanks. I will try to learn how to use the nightly build. But how will I know when |
@ScottHutchinson It will have a "released: vx.xx" tag, such as this ticket. |
@granicz That helps. I wonder if I'm subscribed to this closed issue, will I get notified when that released label gets added? Also, I guess I could subscribe some RSS reader to https://www.nuget.org/packages/Bolero.Server/atom.xml to get notifications of releases. It would be nice if the Nuget Gallery had that built in, but I don't see it now. |
I added that url to a nuget.config file in my HelloWorldBolero repo root folder and ran dotnet restore. But it didn't seem to change anything.
Do I need to put that nuget.config file in each project folder (client and server)? Maybe I need to update my PackageReference elements?
|
with .net core 3.0 preview 6 , I am getting below error:
The text was updated successfully, but these errors were encountered: