We have been fairly busy here with consulting work, product development, website upgrades, new online store etc etc. As I hinted at earlier we were in the process of releasing v2.1 of the Smart Device Framework.
This week we finally released Smart Device Framework 2.1. Although it's a minor release and have cleared all bugs in our bugzilla database we have added some new features. Nick Randolph decided to take the new release for a spin and talks about his experience here. Even though we have just released v2.1, Chris is already talking about v2.2 features here and here! Thanks to Neil, the Smart Device Framework Extensions for Visual Studio has a much cleaner install, more integration with Visual Studio and start menu shortcuts to the help, source, samples etc. As usual, we still offer the Smart Device Framework Community Edition free of charge.
For a list of new changes to the library see here. One big change we did is separate the OpenNETCF.WindowsCE.Messaging into it's own assembly OpenNETCF.WindowsCE.Messaging.dll from OpenNETCF.WindowsCE.dll.
We have also reintroduced support for the OpenNETCF.Windows.Forms.Signature control. Unfortunately it slipped through the cracks with the 2.0 release (mainly my fault as I was responsible for OpenNETCF.Windows.Forms namespace) but it is now back in the 2.1 release with design time support.
For OpenNETCF.Windows.Forms.OwnerDrawnList we added a DrawMode property to keep it in line with the desktop framework. If you use the ListBox2 or SmartList and have some custom drawing code you may want to test your code if you are going to use Smart Device Framework 2.1.
Another cool feature we added to OpenNETCF.Windows.Forms.TextBox2 was the ability to be notified when a Cut, Copy, Paste or Clear event is sent to the TextBox. I have a seperate post on that so if you are interested in that stay tuned :)
If you are a current customer of either the Extension or Community Edition, our online store now has the ability to accept product reviews. Let us know what you like, don't like and want to see in the next version. We are already adding features to v2.2 but are always interested in what our customers and the community want to see.