2/17/2011

These are the release notes for the Windows® Phone Developer Tools January 2011 Update. The January 2011 Update replaces the October 2010 Update previously released.

What’s in the January 2011 Update

What’s in the WPDT Fix

System Requirements

Installation

Uninstallation

Frequently Asked Questions

Known Issues

What’s in the January 2011 Update

The following are included in the Windows Phone Developer Tools January 2011 Update:

Copy and Paste

Copy and paste is now enabled on Windows® Phone 7 in the following controls:

Developers can test the copy and paste functionality in the new Windows Phone Emulator. For more information, see How to: Test Copy and Paste in Windows Phone Emulator. End users can use the copy and paste functionality only after receiving the corresponding update to the Windows Phone 7 operating system.

Most applications already published to the Windows Phone Marketplace do not need to be recompiled to take advantage of copy and paste functionality. Copy and paste will work automatically for end users after they receive the corresponding update to the operating system.

Caution:

In applications that have pivot or panorama controls that contain text boxes, users can unintentionally change panes when trying to copy text. To prevent this problem, open your application, recompile it, and then resubmit it to the Windows Phone Marketplace.

Windows Phone Capability Detection Tool

Detects the phone capabilities used by your application. When you submit your application to Windows Phone Marketplace, Microsoft performs a code analysis to detect the phone capabilities required by your application and then replaces the list of capabilities in the application manifest with the result of this detection process. This tool performs the same detection process and allows you to test your application using the same list of phone capabilities generated during the certification process. For more information, see How to: Use the Capability Detection Tool.

Windows Phone Connect Tool

Allows you to connect your phone to a PC when Zune® software is not running and debug applications that use media APIs. For more information, see How to: Use the Connect Tool.

Updated Bing Maps Silverlight Control

Includes improvements to gesture performance when using Bing™ Maps Silverlight® Control. For more information, see Bing Maps Silverlight Control for Windows Phone.

What’s in the WPDT Fix

After installing the Windows Phone Developer Tools Fix, application developers can deploy XAP files over 64 MB in size to physical phone devices for testing and debugging.

System Requirements

You must have Windows Phone Developer Tools RTW version installed. For more information, see Installing Windows Phone Developer Tools.

Supported operating systems

  • Windows® Vista® (x86 and x64) with Service Pack 2 – all editions except Starter Edition

  • Windows® 7 (x86 and x64) – all editions except Starter Edition

Hardware

  • Installation requires 3 GB of free disk space on the system drive.

  • 2 GB RAM

  • Windows® Phone Emulator requires a DirectX® 10 or later graphics card with WDDM 1.1 driver.

Platforms Not Supported

  • Windows® XP and Windows Server® are not supported.

  • Virtual PC and Hyper-V™ are not supported.

Installation

To install the January 2011 Update

  1. Use the drop-down box to select the correct language.

    The language version of the update must match the language version of the Windows Phone Developer Tools RTW installed on your PC.

  2. Click the download link WindowsPhoneDeveloperResources_<language>_Patch1.msp and follow the instructions.

    Important Note:

    The installation takes several minutes. The installation may indicate that it is 100% complete while it is still finishing. Do not close the installation manually.

To install the WPDT Fix

  • Click the download link VS10-KB2486994-x86.exe and follow the instructions.

Uninstallation

Caution:

If you previously installed the October 2010 Update, and you uninstall the January 2011 update, you will not revert to the October 2010 Update. You will revert to an RTW installation.

To uninstall the January 2011 Update

  1. From Start > Control Panel > Programs > Programs and Features, select Microsoft Windows Phone 7 Developer Resources, and click Uninstall.

  2. From Start > Control Panel > Programs > Programs and Features, select Microsoft Windows Phone Developer Tools, and click Uninstall/Change.

    When the installer dialog box appears, click Repair.

To uninstall the WPDT Fix

  • From the Start > Control Panel > Programs > Programs and Features > View installed updates, select Hotfix for Microsoft Windows Phone Developer Tools – ENU (KB2486994), and click Uninstall.

Frequently Asked Questions

The following are frequently asked questions about the Windows Phone Developer Tools January 2011 Update:

Do I have to install both the January 2011 Update and the WPDT Fix?

No, you can install one, the other, or both.

Does it matter whether I install the January 2011 Update first or the WPDT Fix first?

No, you can install them in any order.

I can already deploy XAP files larger than 64 MB to my phone using WPDT. Why do I need to install the WPDT Fix?

Phone devices that do not have the operating system update that corresponds to the January 2011 Update accept deployment of XAP files of any size using WPDT, even without installing the WPDT Fix. Phone devices that have the operating system update do not accept deployment of XAP files larger than 64 MB using WPDT. To ensure that you can always deploy your XAP files to the latest operating system using WPDT, you should install the WPDT Fix.

Where do I find the Capability Detection Tool and the Connect Tool?

The tools are installed in the %Program Files%\Microsoft SDKs\Windows Phone\v7.0\Tools directory.

The Capability Detection Tool and the Connect Tool are not at the location specified above. What happened to them?

If you previously installed the October 2010 update, then installed the January 2011 update, and then uninstalled the January 2011 update, you have reverted to an RTW installation. You need to install the January 2011 update to access the Capability Detection Tool and the Connect Tool.

How do I confirm that the Windows Phone Developer Tools January 2011 Update installed successfully?

  1. Click Start > Control Panel > Programs > Programs and Features.

  2. On the left navigation panel, click View installed updates.

    If the update installed successfully, you will see “Microsoft Windows Phone 7 Developer Resources - January 2011 Update” in the list.

Known Issues

Default Deployment Target

When you install the January 2011 Update, the default deployment target for Windows Phone Projects in Visual Studio changes to Windows Phone 7 Device. You can change the default target to Windows Phone 7 Emulator by using the following steps:

  1. Close all Visual Studio and Windows Phone Emulator instances.

  2. Delete the contents of %LocalAppData%\Microsoft\Phone Tools\CoreCon.

  3. Restart Visual Studio.

Update to MediaPlayer Behavior

Changing the values of the Volume and IsMuted properties of the MediaPlayer class has no effect if the user is currently playing music from the Zune music library. This limitation preserves the Zune media playback experience by preventing accidental muting.

The following are recommendations for developers:

  • To ensure that the system does not ignore your MediaPlayer settings, start game music playback before you set the Volume, IsMuted, and other properties.

  • Use the Pause method instead of the IsMuted or Volume property to temporarily mute Zune media playback.

  • Allow users to change the background music volume only when game media playback is active.

Text Box Control Rendering Issue

In some situations, selecting text in a text box control can cause your application to stop working. This can happen when a text box has been added to the visual tree, but has not yet been rendered. For example, the following code demonstrates the issue:

 
public MainPage()
{
    InitializeComponent();
    textBox1.Visibility = System.Windows.Visibility.Collapsed;
}

private void button1_Click(object sender, RoutedEventArgs e)
{
    textBox1.Visibility = System.Windows.Visibility.Visible;
    textBox1.Focus();
    textBox1.SelectAll();
}

To avoid this problem, call the UpdateLayout method before calling the Focus method, as shown in the following code:

 
public MainPage()
{
    InitializeComponent();
    textBox1.Visibility = System.Windows.Visibility.Collapsed;
}

private void button1_Click(object sender, RoutedEventArgs e)
{
    textBox1.Visibility = System.Windows.Visibility.Visible;
    textBox1.UpdateLayout();
    textBox1.Focus();
    textBox1.SelectAll();
}

Photo Orientation - EXIF Metadata

Windows Phone does not ship with managed libraries for reading Exchangeable Image File Format (EXIF) metadata from photos. To display portrait images from the photo library, or from the Microsoft.Phone.Tasks.CameraCaptureTask chooser, in their correct orientation, you must use a third-party library or your own code for processing the metadata. This issue applies to the current release and all previous releases of the Windows Phone Developer Tools including RTW.

DecodeJpeg Method

The DecodeJpeg method in the Microsoft.Phone.PictureDecoder class, responsible for decoding a JPEG into a WriteableBitmap object, does not accept the maximum pixel width parameter passed in when used.

 
public static WriteableBitmap DecodeJpeg
    (Stream source,
     int maxPixelWidth,
     int maxPixelHeight
    )

Due to a code defect, the parameter maxPixelHeight is used for both maxPixelWidth and maxPixelHeight. This issue applies to the current release and all previous releases of the Windows Phone Developer Tools including RTW. This issue will be fixed at a later date.

Copyright and Confidentiality Statements

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2011 Microsoft Corporation. All rights reserved.

Microsoft, Bing, DirectX, Hyper-V, Silverlight, Windows, Windows Server, Windows Vista, and Zune are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.