Upgrade to .NET 5 #509
Upgrade to .NET 5 #509
Conversation
- Microsoft.SourceLink.GitHub 1.0.0-beta2-19367-01 > 1.0.0 - System.Drawing.Common 4.7.0 > 5.0.0 - Microsoft.VisualStudio.Web.CodeGeneration.Design 3.0.0 > 5.0.0
|
I don't see any testing guidelines on the repo. I was able to run the web app to test the changes and fire off demo code.
|
|
Will this change mean that our existing .NET Core 3.1 projects will no longer be able to update versions of Electron .NET? |
|
If you were to use the .NET 5 version I think you would need to update your project to .Net 5 as well. From Core 3.1 that should be possible but of course not everyone will want to do that. |
|
Yeah I am not sure we'll want to do that. .NET Core 3.1 and then .NET 6 are the long term support versions from Microsoft. I would still like to be able to get fixes and new features from Electron .NET without having to upgrade to .NET 5. Unless you guys are planning on adding some .NET 5 specific features, is there really any reason to drop .NET Core 3.1 support. Could you not still build and ship both in a NuGet package? |
|
That's probably a better question for Gregor to answer. He is planning out the next milestone release now. |
|
Fantastic - I could really use this version - when is it going to hit nuget (even in preview form)? |
|
I think the new version will only be compatible with .NET 5. However, the 9.31.x version can still be used. I think otherwise we will get mixed up on two tracks. |
|
Is there any ETA on when this will be available on nuget? |
|
@arne309 I still have three weeks vacation. Definitely will publish it in the next few weeks. |
|
It looks like this feature is merged - is there any bug holding from doing a beta release in nuget? |
Upgraded projects from .NET 3.1 to .NET 5.0.
Upgraded WebApp project from TypeScript 3.8 to TypeScript 5.0.
Upgraded NuGet packages to the latest versions:
This addresses issue #491