4 ms·

What do you mean by five different variants? Also, what are the chunks of the ecosystem that were abandoned? Web Forms? Silverlight? UWP? Microsoft has sho

What do you mean by five different variants? Also, what are the chunks of the ecosystem that were abandoned? Web Forms? Silverlight? UWP? Microsoft has shown an amazing ability to modernize and improve the platform without dragging baggage around from one version to the next. We just took an ASP.NET MVC web app developed in 2005 for Windows/IIS and shipped it on linux using .NET core— the conversion took 1 developer just 2 days.

qz2 6y ago
Trivial projects yeah. This is not a trivial project. As for different variants. Two different http pipelines (classic, integrated), OWIN, one obsolete variant of OWIN, whatever is lurking inside .Net core now. WebAPI, MVC, bits of the remains of WCF floating around. Abandoned bits: WCF, WWF, older OWIN pipelines, SignalR and a huge chunk of open source projects and commercial CLR packages. It's a shit show it really is.
- WorldMaker 6y ago
  SignalR is still supported. Though yes, modern "Core SignalR" is something of a rewrite compared to older versions of SignalR, though the biggest backwards incompatible changes are JS client side, not server side .NET side (most of that remains the same once you swap nuget packages), as they dropped the magic JS autogenerated client for a sometimes more sensible "Event Emitter" style client.
- yread 6y ago
  WWF has nothing in common with the other stuff?! It was also one of the shittier MS technologies. Shipping software over decades is tricky: look at the alternatives: what web app from 2005 could you just run today? How has the platform developed over time? PHP, Perl, Python, Java, Ruby... No really clear winner there, IMO
  - qz2 6y ago
    What about AppFabric which tied it and all their ESB stuff together. That was flushed faster than a bag of crack in a police toilet.
nullsense 6y ago
We have a million line SaaS on .NET 4.7.2 running EF 5 that we can't upgrade to .NET Core. We can't do it all in one big bang as it's too much effort and too risky. It will like just continue to rot. We're trying to break it up somewhat and write new parts in .NET Core, but it's an ugly reality staring us in the face.
- andrewf 6y ago
  At work, we sidestepped having to explicitly do a Python 2 -> 3 transition, because we were already rewriting the monolith as a bunch of microservices. Took 7 years.
  - qz2 6y ago
    I’ve watched my current gig push microservices hard. Realistically after 5 years and a lot of investment only 10% of traffic lands on them. Was a waste of money and time.
    - nullsense 6y ago
      For the company yes, but not for your resume right? Resume Driven Development.
      - qz2 6y ago
        That nails it perfectly. It's sad but true.
- qz2 6y ago
  I feel for you

qz2 6y ago

Trivial projects yeah. This is not a trivial project. As for different variants. Two different http pipelines (classic, integrated), OWIN, one obsolete variant of OWIN, whatever is lurking inside .Net core now. WebAPI, MVC, bits of the remains of WCF floating around. Abandoned bits: WCF, WWF, older OWIN pipelines, SignalR and a huge chunk of open source projects and commercial CLR packages. It's a shit show it really is.

WorldMaker 6y ago
SignalR is still supported. Though yes, modern "Core SignalR" is something of a rewrite compared to older versions of SignalR, though the biggest backwards incompatible changes are JS client side, not server side .NET side (most of that remains the same once you swap nuget packages), as they dropped the magic JS autogenerated client for a sometimes more sensible "Event Emitter" style client.
yread 6y ago
WWF has nothing in common with the other stuff?! It was also one of the shittier MS technologies. Shipping software over decades is tricky: look at the alternatives: what web app from 2005 could you just run today? How has the platform developed over time? PHP, Perl, Python, Java, Ruby... No really clear winner there, IMO
- qz2 6y ago
  What about AppFabric which tied it and all their ESB stuff together. That was flushed faster than a bag of crack in a police toilet.

nullsense 6y ago

We have a million line SaaS on .NET 4.7.2 running EF 5 that we can't upgrade to .NET Core. We can't do it all in one big bang as it's too much effort and too risky. It will like just continue to rot. We're trying to break it up somewhat and write new parts in .NET Core, but it's an ugly reality staring us in the face.

andrewf 6y ago
At work, we sidestepped having to explicitly do a Python 2 -> 3 transition, because we were already rewriting the monolith as a bunch of microservices. Took 7 years.
- qz2 6y ago
  I’ve watched my current gig push microservices hard. Realistically after 5 years and a lot of investment only 10% of traffic lands on them. Was a waste of money and time.
  - nullsense 6y ago
    For the company yes, but not for your resume right? Resume Driven Development.
    - qz2 6y ago
      That nails it perfectly. It's sad but true.
qz2 6y ago
I feel for you