PLEASE READ: Welcome to Silverlight for Windows Phone! RRS feed

  • Question

  • Welcome to Silverlight for Windows Phone!  This forum is dedicated to help you get answers to your questions about Silverlight development for the Windows Phone platform.  Please read some helpful FAQ information below to get started.


    Q: Where can I get general information about Windows Phone development?

    Q: Where can I get the tools I need to develop Windows Phone applications with Silverlight?

    Q: What about XNA Game Studio for Windows Phone?

    Q: What is the version of Silverlight on Windows Phone?
    A: Silverlight for Windows Phone is based on Silverlight 3.  Other APIs in Microsoft.* namespaces are available to access key parts of the phone hardware and operating system.  A handful of APIs from Silverlight 3 that don’t make sense in the Windows Phone application model have been removed.

    Q: What APIs from Silverlight 3 are not supported?
    System Information
    Type: System.Windows.Analytics
    Type: System.Windows.GpuInformation

    Type: System.Windows.CrossDomainAccess
    Property: System.Net.Browser.WebRequestCreator.BrowserHttp

    Property: System.Windows.Controls.HyperlinkButton.TargetName

    Local Messaging
    Type: System.Windows.Messaging.ListenFailedException
    Type: System.Windows.Messaging.LocalMessageReceiver
    Type: System.Windows.Messaging.LocalMessageSender
    Type: System.Windows.Messaging.MessageReceivedEventArgs
    Type: System.Windows.Messaging.SendCompletedEventArgs
    Type: System.Windows.Messaging.SendFailedException

    Graphics & Media
    Type: System.Windows.Media.Effects.PixelShader
    Property: System.Windows.Media.Effects.ShaderEffect.PixelShader
    Property: System.Windows.Controls.MediaElement.Attributes
    Property: System.Windows.Controls.MediaElement.Markers
    Event: System.Windows.Controls.MediaElement.MarkerReached

    App Model
    Property: System.Windows.Interop.SilverlightHost.Source
    Property: System.Windows.Interop.SilverlightHost.InitParams
    Property: System.Windows.Interop.Settings.EnableAutoZoom
    Property: System.Windows.Interop.Settings.EnableHTMLAccess
    Property: System.Windows.Interop.Settings.Windowless
    Method: System.Windows.AssemblyPart.Load(System.IO.Stream)

    Out of Browser
    Type: System.Windows.InstallState
    Type: System.Windows.CheckAndDownloadUpdateCompletedEventArgs
    Type: System.Windows.CheckAndDownloadUpdateCompletedEventHandler
    Type: System.Windows.OutOfBrowserSettings
    Property: System.Windows.Application.InstallState
    Property: System.Windows.Application.IsRunningOutOfBrowser
    Event: System.Windows.Application.InstallStateChanged
    Event: System.Windows.Application.CheckAndDownloadUpdateCompleted
    Property: System.Windows.Deployment.ExternalCallersFromCrossDomain
    Property: System.Windows.Deployment.OutOfBrowserSettings
    Type: System.Windows.WindowSettings
    Property: System.Windows.Interop.Content.IsFullScreen
    Property: System.Windows.Interop.Content.ZoomFactor
    Event: System.Windows.Interop.Content.FullScreenChanged
    Event: System.Windows.Interop.Content.Zoomed

    Q: What is the recommended hardware to run the Windows Phone emulator?
    A:Windows Phone Emulator supports GPU peripheral emulation using the host PC’s GPU.  The PC must support DDI version 10 and above and DirectX Version 10 and above. On all other machines, the emulator falls back to software emulation which is not optimized for performance.  You can check if your PC supports the recommended configuration by running ‘dxdiag’ from any command-line window.

    Q: Which APIs rely on device hardware and aren't available in the emulator?
    A:The Accelerometer and Location APIs rely on functionality not available in the emulator.  The emulator does support multi-touch on Windows 7 systems with a multi-touch monitor.  Also note that the emulator does not have all of the Windows Phone 7 Series applications and the types in the Microsoft.Phone.Tasks are not supported in the current emulator.  The one exception is Microsoft.Phone.Tasks.WebBrowserTask as IE is included in the emulator.

    Q: What are some key tips and tricks I should know?

    • Use the hardware virtualization feature of your CPU to get better emulator performance(including the boot time).  Turn on the hardware virtualization setting in your BIOS.
    • Click the “Stop Debugging” button after a debug session instead of closing the emulator.  The next time you debug, the same emulator will be used
    • An emulator can be shared between multiple instances of Visual Studio 2010
    • Always include a splash screen in your app.  Create a 480x800 jpeg named splashscreenimage.jpg, include it in the root of your phone project and set it to be “Content."
    • A good trick to make startup seem even quicker is to make your splashscreen a screen capture of the first page of your application.
    Wednesday, March 10, 2010 12:32 PM