3 ms·

I'm in a .net shop, and I've avoided most of the drama by sticking with .net 4.6/4.7 until now, and just ignoring anything to do with "core". I'm sticking my to

• merb 6y ago
  that wasn't a good move since 3.0 it's really really stable, heck even 2.1 and 3.0 barley changed. 5.0 is basically just a package upgrade (well npgsql+efcore has had some trouble, but that took only a few days) also if you did not use webforms it was basically also just a rename of using statements and impl classes between 4.7 and 2.x
  • gnud 6y ago
    If it's true that there's no real difference in libraries between 4.7 and 2.1, that makes me even more sure I made the right choice. I skipped a load of stress, and didn't even miss any important new knowledge.
    • qz2 6y ago
      There are a lot of changes. Don’t assume that poster is correct. A lot of the core HTTP stack has changed and a whole chunk of third party libraries are abandoned or rewritten entirely for .net core. Anything async is likely to be a complete pain in the ass.
      • merb 6y ago
        Year the http stack was rewritten, But mvc handling was barley different between 4 and Core (besides namespaces)
• qz2 6y ago
  Enjoy that. I’ve got a huge project which is wedged on 4.8 eternally.