3 ms·

.NET 5 Now 'Feature Complete' with Preview 8, Go Live Release Candidates Up Next

28 points by GordonS 6y ago

mikece 6y ago
There is "one .NET" going forward, but it's not bringing all things with it: there are billions of lines of WebForms code in production that will eventually have to be replaced or live in a VM in "support mode." On the whole this is a good thing for the .NET ecosystem. They are striking a very reasonable balance between moving forward wile bringing along what they can and Google's tendency to just pull the plug on stuff with little warning no matter how popular it is.
- ygra 6y ago
  Are there really WebForms codebases that someone would intend to port to .NET Core (if it were available there)? I'd guess most of those are stuck in maintenance mode anyway. Also, .NET Framework doesn't go away and is supported with bugfixes and security fixes since it's part of Windows.
  - GordonS 6y ago
    I work in the enterprise space, yet rarely still see old WebForms projects - most were migrated or shutdown years ago. For those I do still see, there hasn't been a single line of code touched in several years.
- tracker1 6y ago
  "Windows Forms" is listed in the unified platform image... I think that's still around (but windows only). Though other upgrades to an application may take more work for .Net 5/6
  - ygra 6y ago
    Windows Forms is the wrapper around the Win32 API. We forms is the ASP.NET part that mimics how Windows Forms works, where near every look or button click included a server roundtrip (doPostback or so was the JavaScript function named that did this, which then sent pretty much the entire current application state as Base64). Those two things are district, even though I've is intentionally similar to the other. And We forms is part of the things that didn't make it to .NET Core or .NET 5.
    - tracker1 6y ago
      Sorry, in my mind I must have misread WebForms as WinForms... I stopped using WebForms really early on, some monorail or ashx, and then mvc. The performance and state overhead for webforms was really bad imo.
pablo500 6y ago
The article links to another one describing the changes coming with C# 9.0 in .NET 5. As somebody who used to use C# extensively, I find it somewhat shocking how complex, and even convoluted, the language now seems to have become. C# was a lean, but still very capable, language. Competent programmers could quickly get a good grasp of it, and code written by one programmer could generally be understood very easily by others. That's what made it good for large projects with many developers. But now, I'm not sure that that's the case any longer. Even fundamental things like instance initialization and properties seem overly complex. Hopefully it just looks worse than it actually is.

28 points by GordonS 6y ago

There is "one .NET" going forward, but it's not bringing all things with it: there are billions of lines of WebForms code in production that will eventually have to be replaced or live in a VM in "support mode." On the whole this is a good thing for the .NET ecosystem. They are striking a very reasonable balance between moving forward wile bringing along what they can and Google's tendency to just pull the plug on stuff with little warning no matter how popular it is.

ygra 6y ago
Are there really WebForms codebases that someone would intend to port to .NET Core (if it were available there)? I'd guess most of those are stuck in maintenance mode anyway. Also, .NET Framework doesn't go away and is supported with bugfixes and security fixes since it's part of Windows.
- GordonS 6y ago
  I work in the enterprise space, yet rarely still see old WebForms projects - most were migrated or shutdown years ago. For those I do still see, there hasn't been a single line of code touched in several years.
tracker1 6y ago
"Windows Forms" is listed in the unified platform image... I think that's still around (but windows only). Though other upgrades to an application may take more work for .Net 5/6
- ygra 6y ago
  Windows Forms is the wrapper around the Win32 API. We forms is the ASP.NET part that mimics how Windows Forms works, where near every look or button click included a server roundtrip (doPostback or so was the JavaScript function named that did this, which then sent pretty much the entire current application state as Base64). Those two things are district, even though I've is intentionally similar to the other. And We forms is part of the things that didn't make it to .NET Core or .NET 5.
  - tracker1 6y ago
    Sorry, in my mind I must have misread WebForms as WinForms... I stopped using WebForms really early on, some monorail or ashx, and then mvc. The performance and state overhead for webforms was really bad imo.

pablo500 6y ago

The article links to another one describing the changes coming with C# 9.0 in .NET 5. As somebody who used to use C# extensively, I find it somewhat shocking how complex, and even convoluted, the language now seems to have become. C# was a lean, but still very capable, language. Competent programmers could quickly get a good grasp of it, and code written by one programmer could generally be understood very easily by others. That's what made it good for large projects with many developers. But now, I'm not sure that that's the case any longer. Even fundamental things like instance initialization and properties seem overly complex. Hopefully it just looks worse than it actually is.