4 ms·
Trivial projects yeah. This is not a trivial project. As for different variants. Two different http pipelines (classic, integrated), OWIN, one obsolete variant
by 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 agoSignalR 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 agoWWF 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 agoWhat about AppFabric which tied it and all their ESB stuff together. That was flushed faster than a bag of crack in a police toilet.