.NET 5.0
devblogs.microsoft.com
.NET 5.0
1–10 of 466 posts
Re: .NET 5.0
#2With Linux support AOT compliation and other goodies I wonder how many people will prefer writing backends in .NET over Java.
Re: .NET 5.0
#3With Linux support AOT compliation and other goodies I wonder how many people will prefer writing backends in .NET over Java.
No thanks. I've been writing .Net since before day one and quite frankly I've been buggered around enough now to run as far away from this as possible.
Re: .NET 5.0
#4> It’s already in active use by teams at Microsoft and other companies...
This means nothing anymore. MSFT says that about everything they release and users are still often left with the feeling that they are guinea pigs testing a very unfinished product.
> For Visual Studio users, you need Visual Studio 16.8 or later to use .NET 5.0 on Windows and the latest version of Visual Studio for Mac) on macOS. The C# extension for Visual Studio Code already supports .NET 5.0 and C# 9.
Reading this makes me wonder who is still using Visual Studio. That IDE is so bad it's beyond believe. .NET 5 is a standalone runtime which anyone can install. You can write C# in a text editor and build and run it from the command line. Why the hell do Windows developers need to install an entire new IDE in order to use the latest version of the .NET runtime? It's ridiculous beyond belief.
Really shows that Visual Studio Code is the future. All you have to do is install the latest runtime and update the plugin so it shows you suggestions for all the latest language features. No need to install a new version of Visual Studio Code itself.
> .NET 5.0 is the first release in our .NET unification journey.
This might cause confusion. .NET 5 is basically .NET Core 3.2 but has been renamed to .NET 5 so that .NET Framework 4.x users can finally get convinced to move to .NET Core. They just dropped the Core to make it look more appealing to them, but it's still .NET Core.
Re: .NET 5.0
#5With Linux support AOT compliation and other goodies I wonder how many people will prefer writing backends in .NET over Java.
Java has GraalVM whose AOT technology[1] is being adopted by pretty much every framework out there.
Re: .NET 5.0
#6With Linux support AOT compliation and other goodies I wonder how many people will prefer writing backends in .NET over Java.
No thanks. I've been writing .Net since before day one and quite frankly I've been buggered around enough now to run as far away from this as possible.
Interesting, I always felt C# was a step ahead of Java, while the JVM was some steps ahead of the CLR.
Re: .NET 5.0
#7With Linux support AOT compliation and other goodies I wonder how many people will prefer writing backends in .NET over Java.
No thanks. I've been writing .Net since before day one and quite frankly I've been buggered around enough now to run as far away from this as possible.
What would you choose for server code?
Re: .NET 5.0
#8> It’s already in active use by teams at Microsoft and other companies... This means nothing anymore. MSFT says that about everything they release and users are still often left with the feeling that they are guinea pigs testing a very unfinished product. > For Visual Studio users, you need Visual Studio 16.8 or later to use .NET 5.0 on Windows and the latest version of Visual Studio for Mac) on macOS. The C# extensi…
It sounds like you just don't like IDEs.
Re: .NET 5.0
#9> .NET 6.0 will use the same approach, with net6.0, and will add net6.0-ios and net6.0-android
Huge endeavor and launch! Looks like mobile app development will be the same with Xamarin
Re: .NET 5.0
#10the highlights are great. 2 lowlights:
- HttpClient/WebRequest ReadWriteTimeout is silently ignored which can result in infinitely hung sockets when doing synchronous network i/o
- System.Speech is unsupported