4 ms·

Over time what you're implying here is true, but in the short term there are a lot of people stuck on .net Framework and it's difficult to get off of it. It sh

Over time what you're implying here is true, but in the short term there are a lot of people stuck on .net Framework and it's difficult to get off of it. It should absolutely be done, any company with old .net framework solutions that are not actively looking at moving them to .net core is being foolish. But lots of companies are foolish.

Ididntdothis 7y ago
“It should absolutely be done, any company with old .net framework solutions that are not actively looking at moving them to .net core is being foolish.” If it only were that easy to move to Core. I thought I could sneak that transition into a few projects but there are a ton of little obstacles that make such an effort lots of work.
- celticmusic 7y ago
  yep, which is why they should be working on it now. The fact that you can target .net standard with framework means TODAY you can sequester your framework specific things behind DLL's and put everything else on .net core officially. I honestly think there's going to be a huge consulting/freelance market for it soon. I wasn't trying to imply that it's easy, just that everyone should be planning out how to do it so they can do it slowly over the next few years rather than all at once in panic mode. Props to MS for ensuring the two can live side by side the way they have. It makes the transition a LOT easier if you're smart enough to start it early and let it have a long tail. I've personally done this a few times already.
  - Ididntdothis 7y ago
    The other option is to stick to what works and see if MS change strategy again as they seem to be doing very few years.
    - celticmusic 7y ago
      MS has not changed strategies since starting .net core. It's on v3, going on v4. If you're still unsure what the future is going to be, you've missed the boat.
      - Ididntdothis 7y ago
        I guess that’s true. The .NET framework strategy is pretty consistent. I guess I am still traumatized by the mess they have created with their desktop UI toolkits.
        celticmusic 7y ago
        that's a good point about the desktop UI stuff, thankfully I stay away from that area.

Ididntdothis 7y ago

“It should absolutely be done, any company with old .net framework solutions that are not actively looking at moving them to .net core is being foolish.” If it only were that easy to move to Core. I thought I could sneak that transition into a few projects but there are a ton of little obstacles that make such an effort lots of work.

celticmusic 7y ago
yep, which is why they should be working on it now. The fact that you can target .net standard with framework means TODAY you can sequester your framework specific things behind DLL's and put everything else on .net core officially. I honestly think there's going to be a huge consulting/freelance market for it soon. I wasn't trying to imply that it's easy, just that everyone should be planning out how to do it so they can do it slowly over the next few years rather than all at once in panic mode. Props to MS for ensuring the two can live side by side the way they have. It makes the transition a LOT easier if you're smart enough to start it early and let it have a long tail. I've personally done this a few times already.
- Ididntdothis 7y ago
  The other option is to stick to what works and see if MS change strategy again as they seem to be doing very few years.
  - celticmusic 7y ago
    MS has not changed strategies since starting .net core. It's on v3, going on v4. If you're still unsure what the future is going to be, you've missed the boat.
    - Ididntdothis 7y ago
      I guess that’s true. The .NET framework strategy is pretty consistent. I guess I am still traumatized by the mess they have created with their desktop UI toolkits.
      - celticmusic 7y ago
        that's a good point about the desktop UI stuff, thankfully I stay away from that area.