The future of .NET Standard • Hacker News Board

Re: The future of .NET Standard

#81

Post by juststeve » Tue, Sep 22, 2020, 9:32 AM UTC

grezql wrote: post #9

Someone wrote: post #2

Earlier articles in this ongoing series of “how to name things”: - September 2016: Introducing .NET Standard ( https://devblogs.microsoft.com/dotnet/introducing-net-standa... ) - May 2019: .NET Core is the Future of .NET ( https://devblogs.microsoft.com/dotnet/net-core-is-the-future... ) - May 2019: Introducing .NET 5 ( https://devblogs.microsoft.com/dotnet/introducing-net-5/ ) (Yes, the last two are from the same mo…

this is so confusing. .net core .net (before core) .netstandard 2.1 .net 5 what a joke. This coming from someone who used to work as dev in .NET

i would also like to get off the bus

Re: The future of .NET Standard

#82

Post by pjmlp » Tue, Sep 22, 2020, 1:33 PM UTC

WorldMaker wrote: post #62

lostmsu wrote: post #26

Earlier quoted context omitted.

I am not sure about the end of the journey. Lots of legacy .NET Framework code means I will continue targeting .NET Standard 2.0. That's why nobody used 2.1 - it did not support legacy framework. .NET 5 does not solve this problem. Just renaming .NET Core (3+1) to .NET 5 won't magically make legacy code portable. Also, there is still very popular Unity 3D, that can target later framework, but will continue to run on…

My understanding is that Unity is hoping to catch up as soon as some of the final AOT stuff merges from Mono into .NET 6, so "for a while" in the case of Unity is now supposed to be a year or less (given Preview versions).

Unity already has their own AOT, two implementations actually.

Re: The future of .NET Standard

#83

Post by kerng » Tue, Sep 22, 2020, 7:14 PM UTC

cwhiz wrote: post #70

kerng wrote: post #46

Maybe Microsoft should give this whole thing a reboot. After many years working with .net but not following it closely last 2-4 years I'm hopelessly lost what's going on....

Well you missed a whole bunch of commotion. .Net 5 is the new .Net and you don’t need to worry about standard or core or 2.0, 2.1, 3.x, backward compatibility, etc. If you start a new project after .Net5 is released in November, there will be little to nothing to worry about and you won’t have missed much of anything.

That sounds great! Will this have good VS Code support? Being a .net developer having used VS before mostly, I had lots of trouble a little over a year back building and referencing things with VS Code. It was easier to use Go and Python with VS code actually.

Re: The future of .NET Standard

#84

Post by cwhiz » Wed, Sep 23, 2020, 3:15 AM UTC

kerng wrote: post #83

cwhiz wrote: post #70

Earlier quoted context omitted.

Well you missed a whole bunch of commotion. .Net 5 is the new .Net and you don’t need to worry about standard or core or 2.0, 2.1, 3.x, backward compatibility, etc. If you start a new project after .Net5 is released in November, there will be little to nothing to worry about and you won’t have missed much of anything.

That sounds great! Will this have good VS Code support? Being a .net developer having used VS before mostly, I had lots of trouble a little over a year back building and referencing things with VS Code. It was easier to use Go and Python with VS code actually.

Yup. For everything except winform designers. I’ve been exclusively using VS Code for .Net Core 2.1/3.1 for over a year now.