CoreCLR ARM 32-bit progress
github.com
github.com
I tried .NET out on the Pi using Mono, years ago when it was relatively new but after the software floating point OS was deprecated. The weird hardware floating point CPU made it pretty much unusable. Even simple things like DateTime objects would fail to work correctly.
Similar issues were in Java IIRC but they had a special build of that. I think Sony had a fixed build of Mono but I haven't tried it. It will be good to have official .NET support outside of Win 10 IoT.
Why would this cause failing tests though? Does that mean they relied on extended precision?
P.S. In researching this post I noticed that one of my projects (a globe wake lamp) has been included in the latest project book (p108) [2]. First I've heard of this! This is actually an old version and there is a newer write-up on my blog [3].
[0]: https://www.raspberrypi.org/downloads/noobs/
[1]: https://www.raspberrypi.org/blog/oracle-java-on-raspberry-pi...
[2]: https://www.raspberrypi.org/magpi-issues/Projects_Book_v2.pd... [pdf]
.NET Compact and Micro had ARM versions.
There is also an Arduino (AVR) that uses .NET Micro as their OS.
https://www.tizen.org/blogs/dh0922/2016/tizen-.net-developer...
They already went through Meego APIs, replaced by Bada OS C++ APIs, replaced by C and Enlightenment APIs, alongside HTML5 apps.
As a developer I would be weary to invest any resources in so unstable OS design.
I was looking into this just yesterday to see how far away it was, so the timing is really fortunate for me.
Between this and the VS Code builds we should now have pretty solid support for developing .NET on Pi and/or Chromebook, so I'm really excited to get rolling with it, especially seeing as I have some free time this week. I'll try to write up my experiences too in case it helps anyone else.
What kind of .NET runs on Windows 10 IoT though (on the RPi Model 3)??
It is the same .NET Native as on Windows 10 store.