New: Universal Netduino Application template (in the new 4.3.2 SDK)
Posted 09 May 2015 - 06:05 AM
With earlier SDKs, each Netduino mainboard had its own "New Project" template, its own HardwareProvider DLL, etc. While we had strong code reusability, we can do even better (and simplify things a bit in the process).
New Universal Netduino Applications
In the new Netduino 4.3.2 SDK, there is exactly one project template for Netduino. This single universal template creates a project for any modern Netduino mainboard (Netduino 3, Netduino Plus 2, Netduino 2 or Netduino Go).
Universal Netduino Apps using GoBus modules are completely portable between Netduino Go and Netduino 3 too. Once we add Shield Base virtual I/O support to the Netduino Go 4.3 firmware, you will even be able to seamlessly move an app using "Arduino headers/shields" from a Netduino 3 mainboard to a Netduino Go mainboard (with Shield Base) simply by redeploying.
Backwards-compatibile with existing code
We designed the new universal templates with full backwards compatibility in mind. Existing Netduino applications do not need to be rewritten. We have added intelligence to the 188.8.131.52 firmware so that all modern Netduino mainboards maintain strong backwards compatibility with existing code.
Legacy Netduino Templates (optional SDK add-on, for gen1 boards)
While the new universal Netduino Application template does not support the older gen1 boards, we want to make sure that makers can continue getting use out of their gen1 boards for many years. So we have added a "Legacy Templates" installer on the downloads page directly under the Netduino SDK.
Here is what the "New Project" templates look like with the legacy templates add-on installed.
The Universal Future
At //build/ 2015, Microsoft showed off Netduino 3 Wi-Fi mainboards running new Universal Windows Platform (UWP)-derived APIs. As we move into the NETMF 4.4 timeframe, the new Universal Netduino Application template will be the foundation upon which new UWP-enabled apps are built as well. There is so much more to come as we innovate with Microsoft this year. Stay tuned!
The new universal Netduino Application project template makes it insanely simple for developers to use Netduino Apps on any mainboard. Start with Netduino 2. Switch to Netduino Go. Switch to Netduino 3. Simply redeploy.
Please let us know your experiences with the new universal template,
Posted 09 May 2015 - 06:38 AM
Ugh. Just think of what this would have looked like in a few more years, with more than a dozen options.
So much cleaner now, with one universal template.
Posted 09 May 2015 - 08:27 AM
Nice! Now I can use NetduinoGO RgbLed in Netduino 3 projects! Nice.
There was some sort of problem with the setup but it said "Successful" after all:
432sdk_setup.png 24.78KB 4 downloads
and I was able to add a new universal project:
new_project_4_3_2.png 45.52KB 2 downloads
-= Genadij =-
Posted 09 May 2015 - 08:39 AM
Thank you very much for the feedback!
The Netduino SDK installer activates VS2012, VS2013 and VS2015 (including Express editions) in the background. It does this to install the universal Netduino Application template in the "New Projects" dialog. If one of those three Visual Studio versions has a partially-removed or needs-to-be-repaired installation, you could get an error like that.
Regardless: as long as you can create, deploy and debug apps...no worries If you run into troubles just let us know!
Posted 23 June 2015 - 11:30 PM
I installed everything like I was supposed to, but when I create a new project in VS2012 I get this error:
Posted 25 June 2015 - 04:47 AM
Is the NETMF SDK installed as well? It looks like some of Visual Studio's templates/support files are missing/corrupted somehow.
Try uninstalling both the Netduino SDK and NETMF SDK. Then reboot and, before you restart Visual Studio, re-install the NETMF SDK and then the Netduino SDK.
Does that get you up and running?
Posted 02 October 2015 - 12:09 AM
It's nice to see that you continue to support older hardware and dedicated the time to create "Netduino Legacy Templates". I'm glad I found this thread before installing visual studio 2010 along side my already installed 2013.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users