.NET Core 3.0 Concludes the .NET Framework API Porting Project
1–10 of 317 posts
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#2Shouldn't this link to https://github.com/dotnet/corefx/issues/41769 instead since it's redirecting there for discussion?
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#3.NET Core 3.0 was major achievement for Microsoft and I like the air surrounding the project and some around it like Visual Studio Code and Windows Subsystem for Linux.
The teams working for Windows development are overall on a roll these days and it's both sad and a little mysterious how Windows 10 is still struggling with QA issues, decisions like dismantling their internal testing teams, dual control panels and inconsistent design.
I've heard Windows devs speaking up off the record that it is hell to work on with so much boilerplate and ceremony both in practice and politics and with few understanding all the ins and outs of building for their Windows 10 desktop, many restorting to copy & pasting because "it's just supposed to be like that". That makes it a little easier to understand why their aforementioned old control panel is still around even after five years of work on a new one.
I wish they could somehow restructure and streamline and come back to also be able to share the excitement like the .NET Core team are doing right now. Maybe if Windows 10X is a success? Maybe Windows is indeed just getting too big for its own good and the Win32 apps are best just put into one fat virtualized environment for backwards compatibility, like in that upcoming evolution of Windows.
Then write the Windows user land in .NET Core.
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#4Microsoft acting to be a good open-source citizen. Did hell freeze over?
Congratulations. I hope Blazor kills Javascript.
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#5.NET Core 3.0 was major achievement for Microsoft and I like the air surrounding the project and some around it like Visual Studio Code and Windows Subsystem for Linux. The teams working for Windows development are overall on a roll these days and it's both sad and a little mysterious how Windows 10 is still struggling with QA issues, decisions like dismantling their internal testing teams, dual control panels and in…
There are rumors that the WindowsNT kernel will be replaced in the future with a Linux Kernel with a Windows Desktop code on top of it.
Can't wait for it. I know 2020 is going to be the year of the Linux Desktop... but....
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#6Can anyone closer to the .NET community than I am comment on the wider adoption of .NET core on standard line of business applications?
The few places I know that work with .NET are a long way from migrating yet. Are there any similarities with the Python 2/3 port? I imagine language level compatibility makes the transition much easier.
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#7Given that our deployment platform was Linux (for a .Net Core 3.0 project), I was determined to use Linux and VS Code for development. That was a fail; the verbose nature of C# and the Framework APIs make it impossible to be productive without significant help from a full-fledged IDE like Visual Studio. One might think the verbosity can be reduced by clever coding (and adopting a functional style), but that's not so easy. If you're writing a Web App/Service, the Framework APIs and most popular libraries will nudge you strongly to use Dependency Injection throughout the app and implement everything as a class and to extract interfaces out of it.
My wishlist for C# is short:
- Allow functions outside of classes
- Structural typing
- Files and directories already provide excellent namespacing. Adopt it instead of forcing namespace declarations
Btw, Linux as a deployment platform works quite well.
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#8.NET Core 3.0 was major achievement for Microsoft and I like the air surrounding the project and some around it like Visual Studio Code and Windows Subsystem for Linux. The teams working for Windows development are overall on a roll these days and it's both sad and a little mysterious how Windows 10 is still struggling with QA issues, decisions like dismantling their internal testing teams, dual control panels and in…
Nadella has made it pretty clear, whether explicitly or implicitly, that Windows is a dead-end product for them. You could've also deduced this from how they selected their CEOs (cloud guy vs product/software guy or even a sales guy like Ballmer was).
When you've already decided a product is a dead-end, you ignore it and don't spend as much in Q&A. You also try to squeeze your customers for all of their worth, even if that pisses them increasingly more, because you know the product has no future anyway so might as well maximize the revenue at all costs - which is also what Nadella has been doing with all the Windows 10 tracking.
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#9I've tried to port a MVC project to .NETCore 2 a while ago, it was pretty painful mainly due to lack of @helper syntax in views (everything which relied to @helper had to be changed).
Also, from what i saw, nobody is actually in a rush to "move" to .NETCore, most big shops still rely on .Net Framerwork , i still do some occasional work on a project which is using .Net Remoting :)
Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project
#10>With .NET Core 3.0, we’re at the point where we’ve ported all technologies that are required for modern workloads
.net HttpClient is based on outdated cookies RFC, RFC6265(that is 8 years old) is yet to be supported [1]. And what can you do today without good http library?