-
Notifications
You must be signed in to change notification settings - Fork 164
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
Compability with .NET Core 3.0.0-preview-27122-01 #159
Comments
It won't be good practice to keep up with unstable preview versions. This library will only target compatibility with the release version of .NET Core 3.0. |
Any thoughts on when .NET Core 3 will be the default target now that it's released? We're keen to use some of the latest Signal-R capabilities. We can see the Blazor experimental branch already uses it, so is it close to being possible? |
You can use the current library version with .NET Core 3 simply by replacing :
with app.UseRouting();
app.UseEndpoints(endpoints =>
{
endpoints.MapHub<DotNetifyHub>("/dotnetify");
});
|
Many thanks - we'll give that a shot |
When I edit the HelloWorld.WebPack .csproj file to use netcoreapp3.0 in Visual Studio 2019: netcoreapp3.0 I get this error:
Any chance you could update at least one demo to use .NET Core 3.0? Or know how to fix the above? (I've successfully built netcoreapp3.0 apps on this machine before.) |
If you run that csproj from a clone of this repo, then there's a |
Thanks, that did it! Here are the steps:
|
When using DotNetify with .NET Core 2.2 SDK I haven't problem. However, I was forced target the project to .NET Core 3.0 SDK (I need support for the serial port on Linux) and got exception.
IDE: Visual Studio 2019 16.0.0 Preview 1.1
SDK: .NET Core 3.0 v3.0.0-preview-27122-01
The text was updated successfully, but these errors were encountered: