Differences between SDF and existing MSFT .NET?

Last post 12-19-2008 11:23 by ctacke. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 12-19-2008 9:30

    Differences between SDF and existing MSFT .NET?

    I previously posted a question similar to this, but inadvertently put it in the wrong forum and probably worded it poorly as well.

    I’ve looked at OpenNetCF SDF briefly; I’ve browsed through the documentation, and I’ve read online comments that say it’s a wonderful thing, but I’ve never seen anything that summarizes enhancements over the native components (3.5).

    For instance, there is a Button2 control, but there appears to be nothing that tells me what makes it different from the Button control that already exists.  I imagine I could do a method-by-method and property-by-property comparison to see what is different, but I’m essentially lazy, hence the interest in a third-party library to begin with.

    Can anyone point me to a concise source that details the differences?

  • 12-19-2008 11:23 In reply to

    • ctacke
    • OpenNETCF Staff
    • Top 10 Contributor
    • Joined on 07-27-2007
    • Indiana
    • Posts 2,255

    Re: Differences between SDF and existing MSFT .NET?

    The SDF contains several hundred classes and several thousand properties and methods.  There's no real way to give a simple description that says "this is what it does."  In some cases it extends exisitng CF features (like Button2, TextBox2, etc) but in many other places it has features that simply don't exist in the CF at all (in fact most of the CF today is purely new features).

    For those that are different, the simplest way to know what they add is to actually look at the source.  For example TextBox2 derives from TextBox, so basically all of the code for TextBox2 is an extension of TextBox (and in fact much of it could be written as extension methods if we wanted to go that route).

     

Page 1 of 1 (2 items)