March 27th, 2012· The Windows Phone SDK 7.1.1 Update release focuses on providing additional tools and documentation for developing for 256-MB devices.
Detect Application Working Set Memory:
· A new device property value, ApplicationWorkingSetLimit, has been added so that you can use the GetValue(String) method to query the memory available for your application, and to change the way your application works if the device it is running on is a 256-MB device.
256-MB Emulator:
· An additional emulator has been added with the Windows Phone SDK 7.1.1 Update release. You can use this emulator to determine how your application will perform on a 256-MB device if you do not have access to one.
XNA Framework:
· The XNA Framework is fully supported on 256-MB devices, however, an additional document has been added to help you performance-tune your XNA Framework applications
XNA Framework:
· The XNA Framework is fully supported on 256-MB devices, however, an additional document has been added to help you performance-tune your XNA Framework applications
Application Manifest:
· With Windows Phone SDK 7.1.1 Update, you can specify a requirement in the application manifest that will prevent your application from being distributed to users with 256-MB devices.
New Languages and Countries/Regions:
· This update adds support for additional languages, and offers new countries/regions where you can publish your application. We’ve updated the documentation in several areas to support these changes.
February 27th, 2012· This update includes an updated 512MB emulator, as well as a new 256MB emulator image, and Intellisense support to communicate device targeting preferences. Once installed, the WP SDK 7.1.1 update allows you to decide which emulator you would like to deploy your app to.
September 29th, 2011Multi-targeting and App Compatibility:
· You can use the Windows Phone SDK 7.1 to create Silverlight® and XNA Framework projects that target either Windows Phone OS 7.1 or Windows Phone OS 7.0. When you create a new project, you are prompted to select the version that you want to target. You can also upgrade existing Windows Phone OS 7.0 projects to take advantage of the new Windows Phone OS 7.1 features.
· All your apps and games that work on Windows Phone OS 7.0 phones will continue to work seamlessly on Windows Phone OS 7.1 phones.
Multitasking:
· In Windows Phone OS 7.1, several features are introduced that allow an application to perform actions even when it is not the active foreground application.
The Execution Model and Fast Application Switching:
· The execution model is now updated to include a dormant state before tombstoning. When a user returns to a dormant application, it resumes quickly and without displaying the Resuming… message to the user.
Alarms and Reminders:
· You can use the Windows Phone SDK 7.1 to create alarms and reminders that display a dialog box on the screen or play a sound at a specified time.
Background Agents:
· You can now run code in the background, even when your application is not running in the foreground. There are two main types of background tasks: periodic agents, and resource-intensive agents.
Background File Transfers:
· You can now initiate file downloads in your application that continue after the user has navigated away. The file downloads continue to run in the background, even when your application is no longer running in the foreground.
Background Audio:
· Your audio applications can now run in the background. Music continues to play while the user launches other apps, and the user has access to the volume controls.
Media:
· Windows Phone OS 7.1 contains significant media improvements. Improvements include 32-bit color support, support for extensionless media URIs, and support for H.264 in Windows Phone Emulator. Also, the MediaElement uses hardware rendering for improved video quality while using less battery power. You can also now save a ringtone from your application.
Silverlight 4:
· Windows Phone OS 7.1 now includes Silverlight 4.
Sockets Support:
· Your applications can now communicate over sockets using the TCP and UDP protocols. Sockets allow two-way communication with cloud services, and enable scenarios such as instant messaging and multi-player gaming.
Network Information:
· Your applications can now access information about the network and network interfaces. You can determine the mobile operator and network capabilities of a user’s phone, and you can get and set connection preferences and requirements.
Push Notifications:
· The push notification system is now more robust. Toast notifications can now link to specific places within your application and pass parameters. Tile notifications now support two-sided application and secondary Tiles.
Live Tiles:
· Application Tiles pinned to the Start screen now have two sides and they flip periodically, making Tiles both more engaging and more informative. Your applications can have more than one Tile pinned to Start, such as Tiles for different cities in a weather app.
Silverlight and XNA Integration:
· Instead of choosing between Silverlight and the XNA Framework, you can now use both in a single app or game. You can combine the page navigation model of a Silverlight application with the rich graphics power of an XNA Framework application.
Application Performance Analysis:
· Windows Phone OS 7.1 now gives you the ability to profile your apps and games. You can measure the use of system resources such as CPU and memory over time, and navigate directly from the results to your code.
Visual Basic Support:
· Visual Basic is now available for both Silverlight and XNA Framework applications. Visual Basic is fully integrated into the Windows Phone SDK 7.1; you do not need to install it separately.
Advertising:
· The Microsoft Advertising SDK for Windows Phone enables you to monetize your apps and games by including ads from Microsoft Advertising. The Advertising SDK is now fully integrated into the Windows Phone SDK 7.1; you do not need to install it separately.
WebBrowser Control:
· The WebBrowser control now supports Internet Explorer 9 and the benefits of increased performance and HTML5 rendering. You can also programmatically access the cookie collection of a WebBrowser control through the WebBrowser extension methods.
Device Status:
· The Windows Phone SDK 7.1 now gives you expanded programmatic access to a user’s Windows Phone device through the DeviceStatus class. You can now determine whether the device is using the battery or external power, whether a keyboard is available or deployed, the device manufacturer, and more.
Local Database:
· You can now store relational data in a local database that resides in your application’s isolated storage container. Your applications can use LINQ to SQL to perform database operations. New APIs enable programmatic database upgrade scenarios.
Isolated Storage Explorer:
· The Windows Phone SDK 7.1 now includes a command line tool that enables you to list, copy, and replace files and directories in the isolated storage.
Launchers and Choosers:
· The Windows Phone SDK 7.1 introduces several new Launchers and Choosers. From your applications, you can now choose an address, invite players to a game session, or save a ringtone. You can also show a location on a map at a preset zoom level, or show directions between two points on a Bing map.
Contacts and Calendar:
· The Windows Phone SDK 7.1 now gives you read-only access to the user’s contacts and calendar data. You can now differentiate your applications by querying and interacting with the user’s data in ways such as letting the user choose from a list of their contacts and sending them emails, searching for contacts’ birthdays, and others.
Encrypted Credential Store:
· The Windows Phone SDK 7.1 now provides access to a set of cryptography APIs. For applications that require login credentials, these APIs enable you to store the credentials in an encrypted way. Now your users do not have to log in anew each time they use your application.
User Experience Design Guidelines:
· There is a new guide to help you follow best practices for Windows Phone user experience design. This documentation collects advice from the experts who created Windows Phone, and from people who were the designers of many of its first applications. There are more than 40 new topics to help you.
Certification Requirements:
· The application certification requirements are now available online in the MSDN library. The documentation now contains test steps for most requirements. This means that now you can test your applications against the requirements before you submit them to App Hub for certification.
· Windows Phone OS 7.0 and Windows Phone OS 7.1 requirements have been updated.
Marketplace Test Kit:
· The Windows Phone SDK 7.1 now contains a Windows Phone Marketplace Test Kit. The Marketplace Test Kit enables you to test your application against the certification requirements right from Visual Studio. You can also take screenshots of your application by using the new built-in emulator screenshot tool, and submit them using the Marketplace Test Kit.
Camera:
· The Windows Phone SDK 7.1 now gives you programmatic access to the camera on Windows Phone devices, including real-time access to raw frames. This enables you to create scanning and augmented reality applications. You can also access the flash and adjust the focus in your applications.
Pictures Extensibility:
· You can now use App Connect to launch your Windows Phone application from the Pictures Hub, picture viewer, and share picker.
Search Extensibility:
· App Connect is a new way for your applications to seamlessly extend the search experience on Windows Phone. With App Connect, users who search the web with the Search button can launch your application directly from Bing search results.
Application Bar:
· The Windows Phone OS 7.1 Application Bar now has two sizes: default and minimized. The new minimized Application Bar is optimized for use on panorama pages, where space is at a premium.
On-Screen Keyboard:
· Windows Phone OS 7.1 has new on-screen keyboards, such as number-only and formula-optimized keyboards, that you can leverage in your applications.
System Tray and Progress Indicator:
· The system tray now supports opacity and colors. It also includes a progress indicator that you can use to indicate progress in your applications.
OData Client:
· The Windows Phone SDK 7.1 now include the Add Service Reference dialog that enables you to generate a client proxy class. You can also use LINQ queries to access OData resources, and perform client authentication to secure OData services with a login ID and password. There is also improved performance when saving client state.
Globalization and Localization:
· Windows Phone OS 7.1 adds support for 16 additional cultures. There is now support for East Asian languages, including reading and user interface fonts.
Creating Trial Applications:
· You can design and implement a trial mode in your application that enables users to try your application before buying it. There are new topics and samples to help you implement trial mode in your applications.
Windows Phone Marketplace:
· The Windows Phone Marketplace FAQ is now available online in the MSDN library.
August 23rd, 2011Multi-targeting and App Compatibility:
· You can use the Windows Phone SDK 7.1 RC to create Silverlight® and XNA Framework projects that target either Windows Phone OS 7.1 or Windows Phone OS 7.0. When you create a new project, you are prompted to select the version that you want to target. You can also upgrade existing Windows Phone OS 7.0 projects to take advantage of the new Windows Phone OS 7.1 features.
· All your apps and games that work on Windows Phone OS 7.0 phones will continue to work seamlessly on Windows Phone OS 7.1 phones
Multitasking:
· In Windows Phone OS 7.1, several features are introduced that allow an application to perform actions even when it is not the active foreground application.
The Execution Model and Fast Application Switching:
· The execution model is now updated to include a dormant state before tombstoning. When a user returns to a dormant application, it resumes quickly and without displaying the Resuming… message to the user.
Alarms and Reminders:
· You can use the Windows Phone SDK 7.1 RC to create alarms and reminders that display a dialog box on the screen or play a sound at a specified time.
Background Agents:
· You can now run code in the background, even when your application is not running in the foreground. There are two main types of background tasks: periodic agents, and resource-intensive agents.
Background File Transfers:
· You can now initiate file downloads in your application that continue after the user has navigated away. The file downloads continue to run in the background, even when your application is no longer running in the foreground.
Background Audio:
· Your audio applications can now run in the background. Music continues to play while the user launches other apps, and the user has access to the volume controls.
Media:
· Windows Phone OS 7.1 contains significant media improvements. Improvements include 32-bit color support, support for extensionless media URIs, and support for H.264 in Windows Phone Emulator. Also, the MediaElement uses hardware rendering for improved video quality while using less battery power. You can also now save a ringtone from your application.
Silverlight 4:
· Windows Phone OS 7.1 now includes Silverlight 4.
Sensors:
· In addition to the accelerometer, your applications can now access the compass and gyroscope sensors, enabling development of apps and games where the physical device itself is a means of user input. There is also now a combined motion API that provides data for attitude (yaw, pitch, and roll), device acceleration, and rotation rate.
Sockets Support:
· Your applications can now communicate over sockets using the TCP and UDP protocols. Sockets allow two-way communication with cloud services, and enable scenarios such as instant messaging and multi-player gaming.
Network Information:
· Your applications can now access information about the network and network interfaces. You can determine the mobile operator and network capabilities of a user’s phone, and you can get and set connection preferences and requirements.
Push Notifications:
· The push notification system is now more robust. Toast notifications can now link to specific places within your application and pass parameters. Tile notifications now support two-sided application and secondary Tiles.
Live Tiles:
· Application Tiles pinned to the Start screen now have two sides and they flip periodically, making Tiles both more engaging and more informative. Your applications can have more than one Tile pinned to Start, such as Tiles for different cities in a weather app.
Silverlight and XNA Integration:
· Instead of choosing between Silverlight and the XNA Framework, you can now use both in a single app or game. You can combine the page navigation model of a Silverlight application with the rich graphics power of an XNA Framework application.
Application Performance Analysis:
· Windows Phone OS 7.1 now gives you the ability to profile your apps and games. You can measure the use of system resources such as CPU and memory over time, and navigate directly from the results to your code.
Windows Phone Emulator:
· Windows Phone Emulator is now enhanced to simulate sensor data. You can now do initial testing of applications that use sensor data directly in the emulator.
Visual Basic Support:
· Visual Basic is now available for both Silverlight and XNA Framework applications. Visual Basic is fully integrated into the Windows Phone SDK 7.1 RC; you do not need to install it separately
Advertising:
· The Microsoft Advertising SDK for Windows Phone enables you to monetize your apps and games by including ads from Microsoft Advertising. The Advertising SDK is now fully integrated into the Windows Phone SDK 7.1 RC; you do not need to install it separately.
WebBrowser Control:
· The WebBrowser control now supports Internet Explorer 9 and the benefits of increased performance and HTML5 rendering. You can also programmatically access the cookie collection of a WebBrowser control through the WebBrowser extension methods.
Device Status:
· The Windows Phone SDK 7.1 RC now gives you expanded programmatic access to a user’s Windows Phone device through the DeviceStatus class. You can now determine whether the device is using the battery or external power, whether a keyboard is available or deployed, the device manufacturer, and more.
July 28th, 2011· Application platform APIs are now locked; you can feel confident to start getting ready for submitting your apps next month.
· Emulator now has a nifty screenshot capability built in, allowing you quickly snap quality images of your app without the need of separate tools or cropping time. The images are great for use in app submission process or to share on your blog or with folks.
· The profiler has been greatly improved and provides memory profiling.
· As of this drop, you can install NuGet into the free version of the WPSDK tools.
· The drop includes an initial peek at the Marketplace Test Kit; with the RC release, you’ll be able to use the included version of this toolkit to test your XAP file against the same certification testing tools that we use when ingesting apps for the Marketplace. For this refresh, it’s there but not fully functional
June 30th, 2011Multitasking:
· In Windows Phone 7 Codenamed "Mango", several features are introduced that allow an application to perform actions even when it is not the active foreground application.
The Execution Model and Fast Application Switching:
· The execution model is now updated to include a dormant state before tombstoning. When a user returns to a dormant application, it resumes quickly and without displaying the Resuming… message to the user.
Background Agents (Scheduled Notifications and Tasks):
· You can now schedule actions for a future time, and they will occur even if the application is not running in the foreground. The actions that you can schedule belong to two categories: notifications and tasks.
Background Audio:
· Your audio applications can now run in the background. Music continues to play while the user launches other apps, and the user has access to the volume controls.
Background File Transfers:
· You can now initiate file downloads in your application that continue after the user has navigated away. The file downloads continue to run in the background, even when your application is no longer running in the foreground.
Sensors:
· In addition to the accelerometer, your applications can now access the compass and gyroscope sensors, enabling development of apps and games where the physical device itself is a means of user input. There is also now a combined motion API that provides data for attitude (yaw, pitch, and roll), device acceleration, and rotation rate.
Sockets Support:
· Your applications can now communicate over sockets using the TCP and UDP protocols. Sockets allow two-way communication with cloud services, and enable scenarios such as instant messaging and multi-player gaming.
Network Information:
· Your applications can now access information about the network and network interfaces. You can determine the mobile operator and network capabilities of a user’s phone, and you can get and set connection preferences and requirements.
Push Notifications:
· The push notification system is now more robust. Toast notifications can now link to specific places within your application and pass parameters. Tile notifications now support two-sided application and secondary Tiles.
Live Tiles:
· Application Tiles pinned to the Start screen now have two sides and they flip periodically, making Tiles both more engaging and more informative. Your applications can have more than one Tile pinned to Start, such as Tiles for different cities in a weather app.
Silverlight and XNA Integration:
· Instead of choosing between Silverlight and the XNA Framework, you can now use both in a single app or game. You can combine the page navigation model of a Silverlight application with the rich graphics power of an XNA Framework application.
Application Profiling:
· Windows Phone OS 7.1 now gives you the ability to profile your apps and games. You can measure the use of system resources such as CPU and memory over time, and navigate directly from the results to your code
Windows Phone Emulator:
· Windows Phone Emulator is now enhanced to simulate sensor data. You can now do initial testing of applications that use sensor data directly in the emulator.
Visual Basic Support:
· Visual Basic is now available for both Silverlight and XNA Framework applications. Visual Basic is fully integrated into the Windows Phone SDK 7.1 Beta 2; you do not need to install it separately.
Advertising:
· The Microsoft Advertising SDK for Windows Phone enables you to monetize your apps and games by including ads from Microsoft Advertising. The Advertising SDK is now fully integrated into the Windows Phone SDK 7.1 Beta 2; you do not need to install it separately.
Multi-targeting and App Compatibility:
· You can use the Windows Phone SDK 7.1 Beta 2 to create Silverlight® and XNA Framework projects that target either Windows Phone OS 7.1 or Windows Phone OS 7.0. When you create a new project, you are prompted to select the version that you want to target. You can also upgrade existing Windows Phone OS 7.0 projects to take advantage of the new Windows Phone OS 7.1 features.
· All your apps and games that work on Windows Phone OS 7.0 phones will continue to work seamlessly on Windows Phone OS 7.1 phones.
February 5th, 2011Copy and Paste:
Copy and paste is now enabled on Windows Phone 7 in the following controls:
· System.Windows.Controls.TextBox
· System.Windows.Controls.PasswordBox
· Text input fields within the Microsoft.Phone.Controls.WebBrowser control.
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.
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.
Updated Bing Maps Silverlight Control:
· Includes improvements to gesture performance when using Bing Maps Silverlight Control.
September 16th, 2010Updating applications created with earlier versions of Windows Phone Developer Tools:
· Changes have been made to the WMAppManifest.xml and template files. Now that manifest validation has been turned on, you may need to update these files in your older projects. A number of the changes are listed here. However, you can also compare the WmAppManifest.xml, app.xaml and app.xaml.cs files in a new project to the same files in your old projects to determine what has changed and then update your old files accordingly.
The following list shows changes you must make to the WmAppManifest.xml file:
· In the element, change the value of the Genre attribute from NormalApp to apps.normal.
· In the element, change the value of the RuntimeType attribute from SilverLight to Silverlight.
· Remove the PlaceHolderString attribute from the element.
· Add the NavigationPage attribute to the element and set it to the main page of your app. For example: .
Limit to the number side loading of applications on the phone:
· Developer phone registration is the process through which a registered Windows Phone developer may unlock a retail Windows Phone to side load applications for development and testing. A limit on the number of side loaded applications that may concurrently be installed on the phone will be enforced. The default limit will be 10 applications. Attempts to side load more than 10 applications will result in an error. This limit does not affect applications installed via Windows Phone Marketplace.
XNA Framework assembly references:
· The public key token for XNA Framework assemblies has changed. Assembly references in content projects and game projects created using previous releases of Windows Phone Developer Tools must be updated to work correctly. You can do this by removing and re-adding references that do not resolve correctly using the References node in the Visual Studio Solution Explorer.
Character encoding:
· Support for all character encodings will be removed, except for those in the following list.
· utf-8
· utf-16
· utf-16LE
· utf-16BE
· ISO-8859-1
A GamerPrivilegeException is returned if the user does not have content privileges:
If AllowProfileViewing and AllowUserCreatedContent flags are not set in a gamer profile, then the user cannot view profiles or display the gamer card of another user. The following methods now check for these privileges and will return GamerPrivilegeException if the user does not have these privileges:
· Guide.ShowGamerCard(PlayerIndex player, Gamer gamer)
· Gamer.BeginGetFromGamertag(string gamertag, AsyncCallback callback, object asyncState)
· Gamer.GetFromGamertag(string gamertag)
· Gamer.GetProfile()
· Gamer.BeginGetProfile(AsyncCallback callback, object asyncState
The picture sharing mechanism has changed:
· Previously, Windows Phone 7 would place the picture into the Isolated Storage of the application. The picture would then be loaded when the application was launched. Now, when the application is launched, it is passed a string token. To retrieve the picture, the application calls the GetPictureFromToken() method, public static Picture GetPictureFromToken(string token), which takes the token as a parameter and returns a Picture object. You will need to update existing applications.
Deployment and debugging:
While deploying or debugging, if you get the following error: “Application could not be launched for debugging”. First, verify that the application is installed on the target device and that there is no splash screen in the project. Then, uninstall the application and in Visual Studio perform the following steps:
· 1. Add an image file with the name SplashScreenImage.jpg to the project.
· 2. In Solution Explorer, right-click the file and select Properties.
· 3. In the Properties pane, set Build Action to Content.
· 4. Rebuild the application and redeploy it.
Installation on Windows Vista:
· Windows Phone Developer Tools setup blocks installation on Windows Vista and forces the user to install Windows Vista SP2.
July 13th, 2010Framework consolidation:
Consolidated the following DLLs into Microsoft.Phone.dll. Microsoft.Phone.dll contains the following:
· Microsoft.Phone.Shell.dll
· Microsoft.Phone.Controls.Navigation.dll
· Microsoft.Phone.Controls.dll
· Microsoft.Phone.Controls.WebBrowser.dll
· Microsoft.Phone.Notification.dll
· Microsoft.Phone.License.dll
· Microsoft.Devices.dll
· Microsoft.Phone.Execution.dll
· Microsoft.Phone.Info.dll
· Microsoft.Phone.Tasks.dll
Silverlight control template:
· Updated the Silverlight for Windows Phone control templates and changed the default control styles and templates. Along with simple cosmetic changes, the sizing of some controls has changed such that any layouts depending on a specific height / width of a control may be broken. In particular, since the MinHeight / MinWidth constraint has been removed from some controls, you may see controls getting “squashed” if the explicit height set in XAML is too small. Therefore, you should review layouts with the new templates. In general, applications should avoid setting explicit widths and heights on elements unless strictly necessary. Relying on alignment will generally give better results.
Application Manifest File - Changed the following elements in the WMAppManifest file:
· In the element, Genre attribute, the value changed from NormalApp to apps.normal.
· In the element, RuntimeType attribute, the value changed from SilverLight to Silverlight.
· In the element, removed the PlaceHolderString attribute.
Phone Controls:
Removed Microsoft.Phone.Controls.dll. You must remove the following:
· References to Microsoft.Phone.Controls.
· References to the xmlns:mpc namespace declaration.
· Any styles that have a TargetType set to “mpc: …” in the app.xaml.
Additonal work items to consider:
· Use the default ListBox style in place of PhoneListBox (delete the Style tag).
· Instead of PhoneListBoxItemLayout, you can copy the XAML code from the app.xaml file of an old project that used the PhoneListBox and manually add it to your project.
· Use the ToggleButton control and apply a custom template in place of ToggleSwitch and ToggleImageButton.
Page and Frame Classes/ Navigation/Controls:
· Moved phone-specific members of Page and Frame classes to new classes, PhoneApplicationPage and PhoneApplicationFrame in the Microsoft.Phone.Controls namespace. Your builds will break if you use the old types.
API changes as follows:
· PhoneApplicationFrame and PhoneApplicationPage are new classes.
· SupportedOrientations property moved from Page class to PhoneApplicationPage class.
· ApplicationBar property moved from Page class to PhoneApplicationPage class.
· PhoneApplicationState property is new. It helps to save transient data on your page.
· Use the State property in PhoneApplicationPage to store page-specific state instead of Stream property in PhoneNavigationEventsArgs.
· Microsoft.Phone.Navigation namespace has been removed.
· ObscuredEventArgs is a new class in Microsoft.Phone.Controls namespace. It handles obscurity changes in your application.
Removed the following items from Microsoft.Phone.Controls namespace:
· Layout enumeration
· ListView class
· ListViewItem class
· NavigatedEventArgs class
· NavigationEventArgs class
· ToggleControlButton class
· ToggleControlSwitch class
· Added NavigatingCancelEventArgs class and NavigationMode enumeration to System.Windows.dll.
WindowsPhoneEvents:
· Removed the WindowsPhoneEvents class and replaced with PhoneApplicationService class.
· Renamed Pause and Resume with Activated and Deactivated.
· Renamed ApplicationIdleDetection with ApplicationIdleDetectionMode and UserIdleDetectionMode.
Manipulation EventArgs in Silverlight - Changed the following properties:
· Removed the Manipulation.CompletedEventArgs.IsTapEvent property.
· Changed Translation properties to populate only when a pan is detected.
This change affects the following properties:
· ManipulationDeltaEventArgs.CumulativeManipulation.Translation
· ManipulationDeltaEventArgs.DeltaManipulation.Translation
· ManipulationCompleted.TotalManipulation.Translation
· Previously, these values would be adjusted on every finger move and did not respect the system defined dead zones. With this change, the Translation properties are only populated once the user has moved a certain number of pixels (as defined by ITouchSession) away from the original contact point.
Changed the Scale property to return 1 instead of 0. This change affects the following properties:
· ManipulationDeltaEventArgs.DeltaManipulation.Scale
· ManipulationCompleted.TotalManipulation.Scale
· Previously, when a Pinch/Stretch gesture was detected and the scale has not changed, the DeltaManipulation.Scale property would return 0. This made certain mathematical operations more difficult than necessary. Also, if the user started a stretch and then pinched back to the original contact points, the Scale would also report 0 which was confusing. It now returns 1 to signify the scale is 1:1 in relation to its original size. This change will affect any application that uses the IsTapEvent property, or includes code to detect and filter out scale values of 0 or relies upon non-filtered translations. To solve this issue, use OnClick instead of IsTapEvent, or check for a translation and scale of 0 in ManipulationCompleted.TotalManipulation or remove code that may have been adjusting Scale assuming a 0 delta instead of 1.
Push Notifications APIs:
Changed push notification APIs. These changes apply to Microsoft.Phone.Notification and Microsoft.Phone.Shell. The following list shows the summary of changes:
· Changed class, method, and member variable names.
· Removed certain delegates.
· Removed most of the custom exceptions.
· Live tile URLs changed to domain restriction.
Network state API - Changed the following namespace:
· Old namespace Microsoft.Devices.NeworkInformation to new namespace Microsoft.Phone.Net.NetworkInformation.
LicenseInfo Class - Changed the following namespace and class names:
· Old namespace Microsoft.Phone.License to new namespace Microsoft.Phone.Marketplace.
· Old class name LicenseInfo to new class name LicenseInformation. This class contains the IsTrial method.
WebBrowser - Changed the following APIs:
· WebBrowser is now a sealed class. You cannot inherit from it.
· IsScriptEnabled, Source, and Base are now dependency properties.
· NavigatedEventArgs change to NavigationEventArgs.
PhoneNumberChooserTask and PhotoChooserTask:
· Modified the Chooser APIs, such as PhoneNumberChooserTask and PhotoChooserTask, to use delegates for returning data back to the calling application. The Completed event in those classes is fired when data is returned back to the application. You can assign delegates to the Completed event to retrieve the returned data. You must remove any references to ITask.
Accelerometer:
· If you used Microsoft.Devices.Sensors namespace, you must change your implementation to use the latest Accelerometer class design.
Here is the summary of changes:
· Removed abstract base class Sensor.
· Removed generic SensorData class.
· Removed AccelerometerReading structure.
· Accelerometer is now a private/sealed class.
· Changed AccelerometerReadingAsyncEventArgs to AccelerometerReadingEventArgs.
· Replaced AccelerometerStartFailedException and AccelerometerStopFailedException with AccelerometerFailedException.
· Renamed HResult property of AccelerometerFailedException to ErrorId.
Interlocked Class in System.Threading Namespace:
· In the Silverlight System.Threading namespace, the 64-bit managed Interlocked methods are not supported. Use the 32-bit methods for your application.
The following is a list of the unsupported methods:
· Interlocked.Add(Int64, Int64)
· Interlocked.CompareExchange(Int64, Int64, Int64)
· Interlocked.Decrement(Int64)
· Interlocked.Exchange(Int64, Int64)
· Interlocked.Increment(Int64)
Reactive Extensions for .NET Framework:
· Changed namespace from System.Reactive to Microsoft.Phone.Reactive. The new assembly is Microsoft.Phone.Reactive.dll. You must update existing projects to use the new reference assembly.
The following namespaces were consolidated into a single new namespace Microsoft.Phone.Reactive:
· System
· System.Collections.Generic
· System.Linq
· System.Concurrency
· System.Disposable
Note:
· System.Observable.dll and IObservable and IObserver interfaces in System namespace did not change.
System.Windows.Browser:
· Removed System.Windows.Browser.dll because this is not supported. The HTML DOM bridge APIs in System.Windows.Browser namespace are not supported in Windows Phone.
· The HttpUtility class is supported in Windows Phone. It is moving to System.Windows.dll in System.Net namespace. If your application uses HttpUtility class, change the namespace to System.Net.
· Any Windows Phone application that started as a Silverlight 3 application will likely be impacted by this change. The default unhandled exception event handler in the Silverlight 3 application template used a type from System.Windows.Browser.dll.
Application Bar - Changed the following Application Bar APIs:
· The type of the PhoneApplicationPage.ApplicationBar property changed from ApplicationBar class to IApplicationBar interface. The member variable of the PhoneApplicationPage used to be of type ApplicationBar, it has been changed to type IApplicationBar. Since the ApplicationBar class implements the IApplicationBar interface, the code you wrote before will still work.
· The interface change should not affect normal application code that creates or modified the application bar through XAML or code. In cases where the application bar objects are cached, you should use an interface.
· The ApplicationBarIconButton class has a new required Text property. You must set this property before you add the button to the application bar; otherwise, you will get an InvalidOperationException.
Orientation and Layout Updates:
· Orientation: Previously, only the page was rotated, but not the entire application frame. There was a two-phase event system for detecting changes in orientation, [On]OrientationChanging followed by [On]OrientationChanged. In this release, the entire application frame rotates and there is only a single event/override—[On]OrientationChanged. You should remove all handlers for the OrientationChanging event.
· System Chrome: There are fewer layout passes to handle the differences in layout when page transitions occur. There is no visible effect as a result of this change.
· The updates also provided the correct behavior for TransformToVisual and FindElementsInHostCoordinates APIs. Make sure that you remove any code that previously provided workarounds for these APIs.
User Interface:
· Removed UIElement.Effect and the corresponding effects DropShadow and Blur.
New Exception for Xbox LIVE games:
· If a game update is available, Xbox LIVE services will not be available until the player installs the game update. When a game update is available, GamerServicesDispatcher will throw a GameUpdateRequiredException when this method is called from a previous version of the game. Games must handle the GameUpdateRequired exception on Windows Phone and allow the player to confirm requests to update the application.
Application Activation Behavior:
· A second launch of an application that is already running or deactivated causes the termination of the first instance of the application. Any code that assumed a resume of the application should be re-evaluated. Your code should not assume that launching the second instance will bring the previously running instance back to the foreground. For more information, see Execution Model Overview for Windows Phone.
Microsoft.Phone.Shell namespace - Changed the following enumerations:
· Old DownloadInterval to new UpdateInterval.
· Old DownloadRecurrence to new UpdateRecurrence.
XNA Framework:
· While the XNA Framework supports Touch for Windows Phone, it no longer supports Touch for Windows-based games.
· Texture2D.SaveAsGif has been removed.
· Developers must deselect D3DX analysis to run the PIX for Windows performance tool.
· The GamerServiceType parameter has been removed from GamerServicesDispatcher.Initialize.
· GetPartnerToken now requires the AudienceURI parameter. This parameter cannot be null or an empty string.
· In the Windows Phone Emulator, the SkinnedEffect bone index channel must be specified as one of the integer vertex element formats - either Byte4, Short2, or Short4. This same set of integer data formats cannot be used for other shader input channels such as colors, positions, and texture coordinates on the emulator.
· In a previous release, the emulator did not support the VertexElement.Byte4 format for the bone index channel, and we advised developers to override ModelProcessor.ProcessVertexChannel and convert bone index channel data from Byte4 to Vector4. This workaround will not work in this release and must now be removed.
· Any vertex format can be used with any shader input channel on Windows Phone devices, Xbox 360, and Windows.
April 30th, 2010· This release has been tested to work with the final release of Visual Studio 2010.
· An updated Windows Phone 7 OS image for the Windows Phone Emulator.
· A few APIs in the frameworks have been added and or changed. See this MSDN page for more details.
· The documentation has been updated with new and expanded topics. See this MSDN page for more details.
· We’ve provided limited support for launchers and choosers. In cases where the underlying built-in experience is not present launchers and choosers are still not available (i.e. the email chooser asks you to select a contact, but there are no contacts in the emulator and no way to add one).
· Pause/Resume events are now supported.
· If the tools are installed as the admin user, non-admin users are now able to deploy to the emulator.
· A problem with incremental deployment of projects has been fixed.
· A problem resulting in the error "Connection failed because of invalid command-line arguments" being displayed during project creation has been fixed.
· A problem where the Windows Phone node was not appearing in VS 2010 on non-system drives has been fixed.
· Design time skin refresh issues have been addressed.
Find us on Google+
