29 ms·

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

• WorldMaker 6y ago
  This is the "reboot announcement". Starting with .NET 5 there's only one .NET again that matters (though you'll hear lots of legacy support complaints for years to come). 5 is now the highest version number and the next version number is 6 like you would expect. There's no other versions you need to know unless you have to support legacy code (and there, it's probably time to reboot if you are supporting certain types of legacy code).
• cwhiz 6y ago
  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.
  • kerng 6y ago
    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.
    • cwhiz 6y ago
      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.