You have reached the legacy GHI Electronics, LLC website, for the new website please visit here. For the new forum please visit here.

You must be logged in to reply.

Page 1 of 10 out of 94 messages.

Introducing TinyCLR OS: a new path for our NETMF devices

6 likes
Posted 10mth ago
by John_ghielectroncs | Employee
Posted 10mth ago
by John_ghielectroncs | Employee
As you may already know, we recently announced our renewed commitment to Microsoft's .NET Micro Framework (NETMF). Our team is pouring their passion into what they think NETMF should be. Sadly, NETMF is no longer actively maintained by Microsoft. Thankfully though, NETMF's entire source code was released under the Apache 2 license. Due to the breaking changes, trademarks, and copyrights, we are renaming our evolution of NETMF to the TinyCLR Operating System.

GHI Electronics's TinyCLR OS carries all of the improvements found in NETMF 4.4 and forges a new path. For developers, all you need to use TinyCLR OS is a small Visual Studio extension. That is really it! Note that NETMF can still be used side-by-side TinyCLR OS. On the device, you have a choice of loading your device with the NETMF firmware or the new TinyCLR OS firmware.

TinyCLR OS is made for .NET developers. Threading, memory management, timers, even handlers, and everything else you had in NETMF still exists in TinyCLR. As far as the hardware access extensions, TinyCLR OS has a similar API to the Windows 10 IoT Core Extensions API. For example, controlling a pin on a Raspberry PI running Windows 10 is very similar to how pins are now controlled on a FEZ Panda III.

All libraries are downloaded through NuGet. Because of this, there will be no SDK to install or machines to lock to specific versions. Simply use NuGet to download any needed version of any needed library on a per-project basis.

We invite you to try the TinyCLR OS preview today. Again, this is an early preview only but we welcome any feedback. Remember, you do not need to make any changes to your NETMF installation. This preview includes G30 and G80.

As always, we want to make things very easy for you and so today's Tech Talk is an intro to TinyCLR OS:

https://www.youtube.com/watch?v=5GrU80FwFMQ


TinyCLR OS 0.1.0 preview: http://ghielectronics.com/downloads/TinyCLR/TinyCLR.0.1.0.zip
TinyCLR Notes: https://www.ghielectronics.com/docs/350/tinyclr
3 likes
Reply #1 — Posted 10mth ago
by Blue Hair Bob | Hero | 17,792 exp
Reply #1 — Posted 10mth ago
by Blue Hair Bob | Hero | 17,792 exp
I think this is great news. Thanks for taking this on. I hope that it is a huge success.

One thing I wish TinyCLR would have is ... support for Panda 1 and Panda 2. I know that they are old, but I still have a bunch of them. And they were great. If it was possible with a reasonable effort, it would sure to great to have support for them in TinyCLR.

Thanks again for all the great stuff over the years. There have been many projects that I could not have done without you.
Reply #2 — Posted 10mth ago
by EvoMotors | Master | 8,156 exp
Reply #2 — Posted 10mth ago
by EvoMotors | Master | 8,156 exp
Some of us gut left out again... I don't have any G30 or G80.
Reply #3 — Posted 10mth ago
by suitable1 | Master | 7,672 exp
Reply #3 — Posted 10mth ago
by suitable1 | Master | 7,672 exp
EvoMotors says:
Some of us gut left out again... I don't have any G30 or G80.



Operators are standing by!
Reply #4 — Posted 10mth ago
by Mr. John Smith | Legend | 42,263 exp
Reply #4 — Posted 10mth ago
by Mr. John Smith | Legend | 42,263 exp
Will we be able to write MSIL, to have finer grain control over the compiler output?
1 like
Reply #5 — Posted 10mth ago
by Brett | Superhuman | 125,590 exp
Reply #5 — Posted 10mth ago
by Brett | Superhuman | 125,590 exp
EvoMotors says:
Some of us gut left out again... I don't have any G30 or G80.

it's a preview, and you can guarantee that this isn't the final list. I suspect you can be sure that the GHI flagship devices with G120 and G400 are too big a target to leave behind, GHI have actively said that these devices are still "current" and I'm sure they'll get attention at the appropriate point in the development cycle.
2 likes
Reply #6 — Posted 10mth ago
by Gus_ghielectroncs | Employee
Reply #6 — Posted 10mth ago
by Gus_ghielectroncs | Employee
Brett says:

EvoMotors says:
Some of us gut left out again... I don't have any G30 or G80.

it's a preview, and you can guarantee that this isn't the final list. I suspect you can be sure that the GHI flagship devices with G120 and G400 are too big a target to leave behind, GHI have actively said that these devices are still "current" and I'm sure they'll get attention at the appropriate point in the development c

Correct. We are building foundations still. G120 is almost done for example but we didn't want to delay the preview for it. We do not have an inclusive list yet as this is not important just yet.

Again, this is just s preview.
Reply #7 — Posted 10mth ago
by rockybooth | Senior | 3,202 exp
Reply #7 — Posted 10mth ago
by rockybooth | Senior | 3,202 exp
@Gus - what plans to you have for supporting VB?
1 like
Reply #8 — Posted 10mth ago
by willgeorge | King | 33,998 exp
Reply #8 — Posted 10mth ago
by willgeorge | King | 33,998 exp
@John -

I sure would like to see a small sample project for VS 2017.

I just installed VS 2017 and my install looks nothing like what I saw in GUS's sample video.
(A thousand choices on what to install and I did not want to install everything)

A sample project just to see if we can get it all configured correctly.

Thanks for all your hard work!
Reply #9 — Posted 10mth ago
by Gus_ghielectroncs | Employee
Reply #9 — Posted 10mth ago
by Gus_ghielectroncs | Employee
@willgeorge - when installing vs2017 you only need to pick .net on the first page

Page 1 of 10 out of 94 messages.

You must be logged in to reply.