4 ms·
This is great. I have a rather large .NET Standard 2.0 library that I've built for VR projects that would be a big boon in IoT devices. It has a large set of un
by moron4hire 7y ago
This is great. I have a rather large .NET Standard 2.0 library that I've built for VR projects that would be a big boon in IoT devices. It has a large set of unit-of-measure conversions and formatters, some Geospatial features for doing math on LatLngs, audio format decoding, image format decoding, various compression algorithm interfaces, type-safe HTTP requests, and a number of statistical filtering systems such as Kalman filtering of kinematic vectors. It'll be great to be able to reuse all of that code.
And if System.IO.Ports can some day get added to .NET Standard, I've got serial port communication in there too.
The active .NET open source community has been very proactive about upgrading to .NET Standard 2.0. There are a lot of things Microsoft "got right" with 2.0 that are making conversion from .NET Framework a lot easier. For example, my own code (which numbers in the 50kloc range) only took a lite weekend to convert, and most of that was just learning about the new project file format (which is drastically simplified for the better, BTW).
Just wish Microsoft had made their Bluetooth stack a part of .NET Standard instead of jamming it into UWP.
EDIT: I'm having a hard time finding an official spec sheet. Has anyone seen it?
- pjmlp 7y agoI got the news from their mailing list, apparently Meadow F7 will be a subject talk at Ignite, maybe afterwards we get to know more about it.