We no longer sell products directly from the GHI Electronics website, click here for more details. Please find a Distributor to complete your online order. If you have any questions regarding this notice please contact us at support@ghielectronics.com.

Using Gadgeteer after 2016 R1

Last modified September 1, 2016

As of January 1st, 2017, we will be discontinuing .NET Gadgeteer. We will only accept orders for a certain minimum after that date. The 2016 R1 SDK will continue to be available to download and use in conjunction with the .NET Gadgeteer Core 2.44.1100 available from Microsoft. However, future SDKs will no longer include the .NET Gadgeteer SDK component and we will no longer develop it any further.

In order to use Gadgeteer with future SDKs after 2016 R1, you must build the desired drivers and potentially the .NET Gadgeteer Core SDK against that new SDK yourself. You may also be required to update or entirely rewrite the driver or core. Both the core and the drivers may not be able to be updated indefinitely. You can find the source code for our drivers in our Bitbucket repository and the .NET Gadgeteer Core from Microsoft's CodePlex.

Because of the number of modules we have supported over the years, we developed a custom SDK build process that integrates with our entire SDK and that differs from the default one that the .NET Gadgeteer templates use. We have not made this build process available. If you want to use Gadgeteer with an SDK after 2016 R1, you need to manually perform the steps that our installer does or write your own installer so that Gadgeteer knows about your changed modules.

The Gadgeteer designer relies on a hardware definition file, a product image, and the module assemblies being added to the global list. You must tell .NET Gadgeteer where to find the hardware definition file and image and the .NET Micro Framework where to find the module assemblies.

To do so, set the below two registry keys for each module (remove WOW6432Node from the path if you are using 32-bit Windows). To determine what needs to be present, use the keys set by our 2016 R1 SDK or consult the .NET Gadgeteer Core templates as a reference.

The AssemblyFoldersEx key should point to the specific version of that assembly: "C:\Program Files (x86)\GHI Electronics\.NET Gadgeteer SDK\Mainboards\[Product]\NETMF 4.3". The HardwareDefinitionsFolders should point to the base folder for that product: "C:\Program Files (x86)\GHI Electronics\.NET Gadgeteer SDK\Mainboards\[Product]".

If you do not need to use the designer, you can simply update the module driver as needed and manually reference it and the needed Gadgeteer Core assemblies in your project. You will need to instantiate the modules, mainboard, and Program class like Gadgeteer does in Program.generated.cs.

Leave feedback about this document.
Let us know if the information presented here was accurate, helpful and if you have any suggestions.
Leave feedback about this document.
Let us know if the information presented here was accurate, helpful and if you have any suggestions.

* Indicates required fields.
This form is only for feedback not support.
Review our how to find information guide on locating helpful resources.