Breaking news: .NET MF 4.2 Beta 1, VB.NET support, and more
#1
Posted 07 June 2011 - 05:54 PM
#2
Posted 07 June 2011 - 06:27 PM
.NET MF 4.2 SDK
* To use the .NET MF 4.2 SDK, you'll need to uninstall the .NET MF 4.1 SDK/PK and Netduino SDK first. [SDK upgrade instructions]
* After installing the .NET MF 4.2 beta 1 SDK, you can still build .NET MF 4.1 projects for boards with .NET MF 4.1 installed. To do so, select ".NET MF 4.1" as the framework version in your project properties. If you try to deploy a .NET MF 4.2 project to a .NET MF 4.1 board, you'll get a deployment-time error that the assembly versions conflict.
Visual Studio only for this beta release
The .NET MF 4.2 beta 1 is brand new...and during beta the official .NET MF 4.2 SDK only supports Visual Studio (not Express). If you're running Visual C# Express, you'll want to wait for a future beta/RC/RTM version before upgrading.
Visual Basic
* Visual Basic Express isn't supported yet. If you want to test the VB support, you'll need a non-Express version of Visual Studio. You'll also need a Netduino with v4.2 beta firmware...we'll get this ready in a few days.
* Visual Basic uses a small VB support runtime for .NET MF. This is deployed automatically as part of your program. It's about 13KB in size.
Here's a quick Visual Basic "blinky" code sample
Imports Microsoft.SPOT Imports Microsoft.SPOT.Hardware Imports SecretLabs.NETMF.Hardware Imports SecretLabs.NETMF.Hardware.Netduino Module Module1 Sub Main() Dim led As New OutputPort(Pins.ONBOARD_LED, False) Do led.Write(True) Thread.Sleep(250) led.Write(False) Thread.Sleep(250) Loop End Sub End Module
We're very excited about .NET MF 4.2. More to come...
Chris
#3
Posted 07 June 2011 - 08:03 PM
That's not fair!!!Visual Basic
Visual Basic Express isn't supported yet. If you want to test the VB support, you'll need a non-Express version of Visual Studio.
Microsoft, if you read this: Visual Basic Express feels discriminated!
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#4
Posted 07 June 2011 - 09:13 PM
#5
Posted 07 June 2011 - 09:15 PM
#6
Posted 07 June 2011 - 09:18 PM
Great question!Other than VB support ? What new features come with that ?
- New AnalogInput and PWM objects
- FTP support
- StringBuilder
- RegEx (coming soon)
- Updated cryptographic primitives
- Remote update infrastructure (may not be applicable)
- Lots and lots of bug fixes
- Etc.
#7
Posted 07 June 2011 - 10:25 PM
#8
Posted 07 June 2011 - 10:29 PM
Firmware updates are still done via MFDeploy. There is some potential for remote update...but we'll have to see how much flash/RAM that takes. That said, it's certainly possible to create a bootloader which reflashes the MCU from an SD card.And the update firmware from sd card? Has some news in this firmware?
Chris
#9
Posted 07 June 2011 - 10:37 PM
Hi João,
Firmware updates are still done via MFDeploy. There is some potential for remote update...but we'll have to see how much flash/RAM that takes. That said, it's certainly possible to create a bootloader which reflashes the MCU from an SD card.
Chris
Yes the idea load from bootloader it's better!
Is very difficult to implement?
Mello
#11
Posted 08 June 2011 - 01:45 AM
Maybe a few days of work for someone. You could either customize TinyBooter to support FAT and look for a file on the SD card during boot...or you could replace TinyBooter with a tight, optimized custom project. The first of those options is much simpler: all the pieces are there.Yes the idea load from bootloader it's better!
Is very difficult to implement?
Chris
#12
Posted 08 June 2011 - 09:22 PM
#13
Posted 08 June 2011 - 09:23 PM
Also, you might be able to adapt the new "remote update" functionality pretty quickly. You'd just need to read the new firmware from the SD card instead of from flash...Yes the idea load from bootloader it's better!
Is very difficult to implement?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users