Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing .NET Standard

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

21–30 of 154 posts

Re: Introducing .NET Standard

#21

Post by bmurphy1976 »

I can't really make heads or tails of this, it's still fairly complicated and I'm just not invested enough in it to read everything with a fine toothed comb.

What I want to know is, will the sync (not async/await) methods be available on Linux on .NET Core? We've been struggling with that, the move to async/await is a major rewrite of our legacy application codebase and for what we do Mono has been a constant thorn in our side.

In an ideal world the old sync APIs would just work and we'd be able to move forward with .NET Core as it stabilizes and get off Mono without a major rewrite.

Re: Introducing .NET Standard

#22

Post by l3m0ndr0p »

One Library to rule them all, One Library to find them; One Library to bring them all and in the darkness bind them

It's nice to see MS making this effort to involve a community of developers in an open-like forum. But the road to hell (MS) is paved with good intentions.

Re: Introducing .NET Standard

#23

Post by sillysaurus3 »

Analemma_ wrote: post #16

I understand that Microsoft has to clean up a lot of legacy baggage around this ecosystem, and it does look like the way forward is much clearer and nicer, but man, was there any way this could've been done without another ".NET "? I'm still figuring out .NET Core/4.5/Framework and all the ASP naming zaniness... and I'm a .NET developer! I do trust Microsoft that this is really, truly the last time this will have to…

http://www.joelonsoftware.com/articles/fog0000000339.html

Re: Introducing .NET Standard

#24

Post by ep103 »

Analemma_ wrote: post #16

I understand that Microsoft has to clean up a lot of legacy baggage around this ecosystem, and it does look like the way forward is much clearer and nicer, but man, was there any way this could've been done without another ".NET "? I'm still figuring out .NET Core/4.5/Framework and all the ASP naming zaniness... and I'm a .NET developer! I do trust Microsoft that this is really, truly the last time this will have to…

I agree 100%.

So anyone care to take a stab at it? How does this differ from .Net Core?

Re: Introducing .NET Standard

#25

Post by wmccullough »

ep103 wrote: post #24
Analemma_ wrote: post #16

I understand that Microsoft has to clean up a lot of legacy baggage around this ecosystem, and it does look like the way forward is much clearer and nicer, but man, was there any way this could've been done without another ".NET "? I'm still figuring out .NET Core/4.5/Framework and all the ASP naming zaniness... and I'm a .NET developer! I do trust Microsoft that this is really, truly the last time this will have to…

I agree 100%. So anyone care to take a stab at it? How does this differ from .Net Core?

The article literally states the difference.

Re: Introducing .NET Standard

#26

Post by rch »

MichaelGG wrote: post #13
rch wrote: post #8

Earlier quoted context omitted.

Excited? Having just inherited a previously outsourced ASP.NET MVC application, I feel like announcements like this ammount to tiny, tentative steps towards tolerable. Portability work should have started over a decade ago.

Portability work started nearly 2 decades ago. .NET has been multiplatform from the start. Around the first release they even had an "open" source version that ran on BSD, thought not with all the libraries.

I get that you can jump through certain hoops to make cross-platform development possible, but the applications I've seen are 'all-in' with MS (even to the point of inappropriately depending on system services like ftp). Portability simply isn't the norm, and it's disingenuous to claim otherwise.

Re: Introducing .NET Standard

#27

Post by PercussusVII »

ep103 wrote: post #24
Analemma_ wrote: post #16

I understand that Microsoft has to clean up a lot of legacy baggage around this ecosystem, and it does look like the way forward is much clearer and nicer, but man, was there any way this could've been done without another ".NET "? I'm still figuring out .NET Core/4.5/Framework and all the ASP naming zaniness... and I'm a .NET developer! I do trust Microsoft that this is really, truly the last time this will have to…

I agree 100%. So anyone care to take a stab at it? How does this differ from .Net Core?

It's the API definition that will be shared by .net Core/full framework/asp.net/xamarin.

Re: Introducing .NET Standard

#28

Post by wmccullough »

wodencafe wrote: post #17

Nothing about Linux, probably because there is no Linux Consumer Market. Looks like Microsoft's EEE strategy is alive and well. This is nothing more than a clever ploy by Microsoft to regain control of C# from the community, becoming the gatekeeper of the new ".NET Standard" library... rather than opening up some of their coveted, proprietary codebase. (Winforms) TL;DR Micro$oft being Micro$oft

Don't feed the troll folks, they need to learn to buy tinfoil on their own.

Re: Introducing .NET Standard

#30

Post by mbesto »

Analemma_ wrote: post #16

I understand that Microsoft has to clean up a lot of legacy baggage around this ecosystem, and it does look like the way forward is much clearer and nicer, but man, was there any way this could've been done without another ".NET "? I'm still figuring out .NET Core/4.5/Framework and all the ASP naming zaniness... and I'm a .NET developer! I do trust Microsoft that this is really, truly the last time this will have to…

Does anyone have a breakdown of how .NET Core/4.5/MVC/etc interact, are different, etc?
Post reply on HN