The .NET Gadgeteer Core installer includes the core libraries and end user project template for Microsoft .NET Gadgeteer. This is a prerequisite for end users to build and deploy .NET Gadgeteer projects. It includes a single project template in the New Project dialog in Visual Studio/Visual C# Express under the Gadgeteer tab - ".NET Gadgeteer Application". This template uses a graphical designer built for Visual Studio or Visual C# Express which allows end users to visually configure .NET Gadgeteer hardware builds and then write the software logic for that hardware in C#.
The .NET Gadgeteer Builder Templates installer is for hardware vendors who are building modules, mainboards or kits comprising multiple modules/mainboards. This adds additional project templates for modules, mainboards and kits. Each template includes instructions on how to use it, and automatically builds an MSI installer which can be distributed to end users.
If you are a prospective module or mainboard builder you should also look at the Module Builder's Guide and Mainboard Builder's Guide, which includes the full specifications for what it means to be ".NET Gadgeteer compatible" and other helpful examples and guidelines.
Neither installer includes libraries for specific hardware modules/mainboards, so by themselves these installers do not enable users to use .NET Gadgeteer hardware. Hardware manufacturers should release installers (based on the templates above) for their hardware.
Microsoft .NET Gadgeteer Core
Version 2.41.401 30 November 2011
Version 2.41.401, 30 November 2011
- Fixed installer bug causing Visual Studio Designer to not upgrade correctly
- VC# Express installation fails if VS is also installed and VS and VC# do not share the same directory root
i.e. if VC# Express is installed under where VS is, e.g. C:\Program Files\Microsoft Visual Studio 10.0\ then it works OK.
- DaisyLink assigns global addresses but it could use per-bus addresses (normally one bus per socket) to increase total addressable devices
- Designer should track most recently used Mainboard and use that by default in a new project
- Designer does not examine MinimumGadgeteerCoreVersion XML tag right now, so if hardware requires a newer version of GadgeteerCore than the one installed, this does not surface until deployment time (as a link error).
Version 2.41.400, 25 November 2011
- Web client and web server libraries moved from Gadgeteer.dll into separate assemblies Gadgeteer.WebServer.dll and Gadgeteer.WebClient.dll. These are referenced by default in the app template. API location moved from GTM.NetworkModule to Gadgeteer.Networking.
- Cloud library moved from GadgeteerCore into separate dll MicrosoftResearch.Gadgeteer.Cloud.dll, and not referenced by default from app template. GadgeteerCore MSI still includes the DLL though (so Add Reference works)
- Added I2C transactions API to Gadgeteer.Interfaces.I2CBus class
- System.Threading and Microsoft.SPOT.Touch references added to App Template
- References created by Designer now set SpecificVersion=false so that newer versions of module/mainboard libraries are picked up by projects
- Designer now deletes references and "usings" when a module/mainbaord is no longer used by a project
- Fixes to how DisplayModule handles switching between display types and display <-> headless.