While it was annoying that .NET Standard 1.x removed a bunch of API's, why were some added back in .NET Standard 2.0 in non-working states?
All that did for me was take compile time errors and turn them into run-time errors which is infinitely worse. I know this decision was likely made long before you joined Microsoft, but I was hoping you could shed some light on this very strange and consumer hostile decision.
IAMA_HUNDREDAIRE_AMA5 karma
While it was annoying that .NET Standard 1.x removed a bunch of API's, why were some added back in .NET Standard 2.0 in non-working states?
All that did for me was take compile time errors and turn them into run-time errors which is infinitely worse. I know this decision was likely made long before you joined Microsoft, but I was hoping you could shed some light on this very strange and consumer hostile decision.
View HistoryShare Link