Following on from my previous post, I've had it confirmed by Microsoft that currently Visual Studio 2010 doesn't support .Net Micro Framework V4. It looks like it does, but it doesn't. Shame as VS2010 is very nice to work with. I guess we will just have to wait for an update to .NET MF before we can use VS2010.

 

In summary, it doesn't work.

The problems I've seen are with the RC version of VS2010, hopefully some of these might be fixed in the RTM version, otherwise I guess a patch for .NET MF will be required.

The Setup:

• Install VS2010

• Install Device Solutions SDK for the Meridian/P

• Try to install .NET Micro Framework v4 – this fails as it requires Document Explorer 2008.

• Install VS2008

• Install .NET Micro Framework v4

 

Once you've got that lot installed you can happily build and debug Micro Framework projects in VS2008:

 

 

However whilst creating a new MF Console application in VS2010 appears to work initially you get a load of broken references and the framework is missing:

When you try and build the project MSBuild crashes.

The missing references and MSBuild crash are because of a missing target in the .csproj file. If you add in <Target Name=”SplitProjectReferencesByType” /> and reload the project then the references appear correctly:

 

However the framework is still missing and the project wont compile:

 

Unfortunately as yet I have no idea how to get a v4 Micro Framework project working in VS2010, so for now stick to VS2008 folks.

 

 

I'm a long term C# developer, from .net 1.0 to working day to day in .Net 3.5, so the thought of being able to write code for embedded devices in C# with the Dot Net Micro Framework is to good to be true.

However, it didn't take long before the Micro part of the Micro Framework took hold and the penny dropped that it really was micro and the CLR was different, so I thought I would share my initial findings as if you are coming into Micro Framework development like me with a history of WinForms and ASP.NET it can feel like a big leap back in time.

A quick look at the Add Reference Dialog Box tells the story.

A V3 Micro Framework Class library project Add Reference dialog box:

 

Compare that the C# 3.5 WinForms project Add Reference dialog box:

Somewhat of a difference! I have intentionally put the WinForms project at the NUnit references to highlight that they are not available for the micro framework whilst being in the GAC. Actually at present I have not found any unit testing framework for the micro framework, even the MS Test framework is missing from the references.

Another major loss is the lack of Generics. No <T> in Micro Framework projects. Apparently this would have made the underlying image to big, which is a real shame as generics adds a huge amount of value and cuts down on a lot of repeated code. And yes, this means no List<T> and it's back to ArrayList of object - ouch!

Many of the day to day tools that existing C# developers may be use to using also don't function with micro framework projects. Reg-Gate's popular Ants performance and Ants memory profilers don't work (as of V5.1) which is a huge shame as memory usage and performance are especially important for embedded systems. NUnit doesn't care much for the micro framework either, although I've only tried V2.4.8 which complained about Generics. I could go on – in short don't assume your favourite tool/component will work with the micro framework!

The good news is that it's not all bad news!

Reflector works a treat (is their nothing that program can't do!).

 

 

Resharper still does it's thing, I'd be lost with out it!

The .csproj is still a MSBuild file.

Many of the great C# 3.0 features work (e.g. Auto-Properties, var)

You can still write separate class library projects as with regular .net so component reuse is really easy and this should help the unit testing story (if only I could find a framework!).

It's still one of the best IDE's I've tried for embedded development and C# is a great language!.

I've started tinkering around with the .NET micro framework and wanted to share my experiences with it as well as other general .Net code whilst not littering my other blog with .Net specific as that blog is supposed to be more about my products. I had IImplement.Net laying around not doing anything so I decided to put it to good use.

About Me:

One of my interests is the hardware and software combination so I was really excited to see Microsoft release the .NET micro framework and that I can build a peripheral for the PC and write the code for it in C# using Visual Studio then push it down to a embedded device as well as writing the application running on the PC in C# as well.

 

My background is Chemistry and a particular interest is lab automation and instrumentation, I'm also into home automation as a result some of the postings will reflect this.

 

.Net Micro Framework Hardware:

It's mid 2009 and these times are hard, I don't have £300+ to spend on a development kit and I guess many of you don't either, so I wanted to start with something that was well priced, easy to upgrade, had good features and more over that would be usable in a standalone product.

 

Introducing the Meridian/P:

 

This is a tiny (2”x2”) prototype board (the Meridian is even smaller!) available from device solutions.net which looked perfect for what I wanted. It's a heavily cut down version of the Tahoe-II with connectors for the IO and TFT screen, a single user switch & led plus a mini-Usb B socket, 8MB SDRAM, 4MB flash and that's basically it, the rest is down to your electronics and programming skills to use the 27 GPIO pins with RS232, SPI, I2C and PWM functions.

 

The thing I also really liked about the Meridian/P is that it's something I could easily use in a final working product (perhaps not a commercial one) as it really has little extra on it and the price is good (with shipping and tax it cost me £82 for a single board), the Meridian CPU looks like it would be more than happy going into a commercial product and is even cheaper.

 

Typical current consumption for the device is 5mA/2.6mA for 5V/3V which also makes it ideal for small projects, even battery powered ones.

 

There are a number of other prototype systems available, one of the reasons it's taken me till V3 of the framework is finding a decent development kit at a price I was willing to pay, now there are a couple of basic solutions and some really good ones for a bit more, the options are becoming better all the time.

 

Here's some photo's of the Meridian/P and Schmart Board(tm)'s that I hope to build up some fun bits on.

 

 

Packaging for the Meridian/P

 

Meridian/P with 2 AA Batteries to give an idea of it's size.

 

A SchmartBoard(tm) physically (not electrically) connected.

 

SchmartBoards(tm) and Meridian/P.