Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Inside the Mango Developer Tools: App Platform

10 minutes, 27 seconds


Right click “Save as…”

Join Brandon Watson as he interviews the people behind the next release of Windows Phone, Mango. In this installment he chats with Andrew Clinick- one of the people behind the new App Platform.

Windows Phone will challenge the way people think about apps. Today their usefulness is measured by what can be done within the app, but we see the promise of apps in how they can be integrated directly into the core experiences of the phone. In addition to making it easier to get timely notifications and updates from apps right from the Start Screen, the Mango release will also surface apps as part of search results and within Windows Phone Hubs.



Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • someoneelsesomeoneelse

    what about c++?

  • Robert VargaRobert Varga

    C++? I think that Microsoft is doing it right - they say that users are more than devs. You can do just this, this and that, but not all, at all. Users>Devs, that's "why" API, not close-to-the-metal.

  • MJ App FactoryMJAppFactory In God We Trust -- all others pay cash

    We do all our stuff in C#, but there's a huge glitch -- lack of dynamic type support for reference classes and interfaces.  As I understand it, the .NETCF team has chosen not to implement Reflection.Emit, therefore breaking a DLR requirement for the dynamic type, and therefore making it impossible for app developers to implement some (not only cool but) advanced technical requirements.

    If this feature isn't available in the developer tools and in Mango soon (like immediately), its absence will represent only one more reason for us to look elsewhere (possibly Cupertino?).  This is not the first real problem with .NETCF, and it's certainly not biggest.  But this one straw is feeling pretty heavy right now on this particular camel's back.

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.