3 ms·
I somehow doubt it, most of the APIs (with the notable exception of some of the reflection APIs) are at parity and the language is the same. This is more like
by hurricaneSlider 8y ago
I somehow doubt it, most of the APIs (with the notable exception of some of the reflection APIs) are at parity and the language is the same.
This is more like a major library dropping support for a legacy runtime going forward.
- svick 8y agoWhat reflection APIs are you talking about? Do you mean things like AppDomain and remoting?
- hurricaneSlider 8y agoYes, at least when I last checked, that stuff wasn't present.
- caseymarquis 8y agoWhen porting some reflection heavy code to .net standard I encountered several breaking changes. They were all easily fixed by using GetTypeInfo(), which is where a lot of reflection functionality seems to have moved. I remember reading that it was for performance improvements.
- davidfowl 8y agoWhat version of netstandard?
- caseymarquis 8y agoI just checked the project.json from that library and it appears to have been 1.6.0. It was a while back. Also, thanks for SignalR! It's a great library!