Mark Arteaga

Here is a list of known issues for design time controls.  If you find more please let us know.  These will all be fixed in the next Beta release

Issue 1: When a smartlist is dropped on a form the size is 0,0

Workaround: Resize the control to a appropriate size.

Issue 2: When deleting a combobox2 from a form a coredll error is thrown

Workaround: Click OK and the combobox will be deleted from the form

Issue 3: When deleting an either an inkx or voicerecorder control it looks like the Paint of the base class gets run.  It will render on the form but you can't select, move, delete the control and there is no variable declared for it.

Workaround: After you delete the control, save the form and close the form in designer and re-open it.  The control rendering will be gone.

Issue 4: StatusBar/StatusBarPanel still needs to be ported

Workaround: Create the control manually through code.  This will be resolved in the next release.

Issue 5: ColorDialog has no design time support

Workaround: Create the control manually through code.  We are working on this issue and hoping to have a resolution by release.

Smart Device Framework 2.0 Beta 1 from OpenNETCF has been released.  We have worked really hard to getting this ready and the redistributables for Beta 1 are now available.  The SDF2.0 documentation is also available online.

A lot of work was done throughout the whole SDF but some of the major changes was supporting the the new design time framework for controls for Visual Studio 2005.  Throughout the process we also decided to change some of the class names that ended with 'Ex' to '2'.  For example, OpenNETCF.Windows.Forms.ProgressBarEx is now OpenNETCF.Windows.Forms.ProgressBar2.

There are still some remaing minor issues with some controls and design time support for Visual Studio 2005.  See this post for some of those issues.

Also, check out the new Licensing Class available in the SDF 2.0.  It works the same as the full framework class so if you are looking to license your .NETCF application to your users this will help.

In a future post I will be writing some tips for creating and migrating controls for Visual Studio 2005.