Mobile development features in the next version of Visual Studio

The Visual Studio for Devices blog has some early information about Windows Mobile developer features in "Orcas" (code name for VS 2007). Current information is for managed development only. Native development information will be posted soon.

  • Add support for the next version of .NET Compact Framework (v3.0 or v2.x)
  • Continue to support .NET CF 2.0
  • Remove the templates for .NET CF 1.0

    • Your existing .NET CF 1.0 projects will be migrated to 2.0 if you wish to use them in Orcas.
    • You can continue to use VS 2005 side by side on the same machine to work with .NET CF 1.0 applications.

  • You will not see any project templates for Smartphone 2003 as it only supports .NET CF 1.0
  • The Windows Mobile 5.0 Pocket PC and Smartphone SDKs will be included in the box
  • Future SDKs from the Windows Mobile team will install seamlessly on Orcas much like you install the Windows Mobile 5.0 SDK today
  • Managed templates for the next version of Windows CE will be added (just like CE 5.0 is supported today)

You can track progress on these features on the VSD blog. Amit Chopra from the VSD team would love to hear your feedback on what mobile developers want to see in Orcas.

Comments (5)

  1. Colin Bowern says:

    Any word on advancements in the mobile web development side?

  2. MSDNArchive says:

    Colin – nothing to announce yet, but you’re welcome to post your comment in the VSD blog.

  3. Oleg says:

    I think its really bad (stupid 🙂 ) idea to remove .NET CF 1.0 support

  4. Jeff Lewis says:

    I love WindowsMobile, but I have to say this – the distribution model is NOT the same as for desktop OSes.

    For one thing, a desktop system can be piecewise updated to replace old hardware when it becomes unsupported – right down to the motherboard – but with WM devices, generally an upgrade means a new device entirely – and they aren’t cheap.

    What has to happen and preferably by WM6 is to decouple the driver and system more so that a person can buy the OS and upgrade without involving the manufacturer (much as we do with WinXP).

    If that can’t happen, then .NET CF has to be agnostic to the platform. Trying to force upgrading to get .NET CF 2.0 just won’t work. This is especially true of Smartphone 2003SE which already doesn’t support CF 2.0.

    Smartphones aren’t cheap.

    Cheap phones aren’t smart.

    But way more cheap phones are sold than smart ones.

  5. Vijay2008 says:


    I am sorry for posting a different question into this topic. I have been developing video capture application and saving to the file using Microsoft DirectShow APIs (This is a sample code given by Microsoft). While the same code runs on WM6 device without any issues and I was able to save a 1 mintue video file in ASF format, I was not at all successful in doing it in a WM5 device. All I get is 2-3 frames of the captured video in the file saved. Can you please give me some pointers on whether this could be due to a older version of the codec in the WM5 device? If so, how do we verify the same and update it since there is no direct access to DLLs present in the Windows folder of the device.

Skip to main content