No big deal.
DisclaimerAll entries in this blog are my opinion and don't necessarily reflect the opinion of my employer.
No big deal.
I’ve updated my WinmdDiff tool to version 1.2 to show not only the new types but also the new members!
As you can see, we’ll have a new
RecordedCalls folder where the recorded calls will be stored in the existing type
The new types are shown in bold like the
UserProfilePersonalizationSettings class that provides the new
TrySetWallpaperImageAsync method: a great opportunity to add a desktop wallpaper changing feature to my NASA Pix of the Day application!
If you don’t know where to find the Universal .winmd files for each version, go to C:\Program Files (x86)\Windows Kits\10\References\Windows.Foundation.UniversalApiContract\126.96.36.199 and get the documentation .xml file from the localized folder
This file is used to show the summary of documented types and members.
If you don’t install the SDKs, get the .winmd files directly from the Windows\System32\WinMetadata directory
UPDATE: a new version has been published with the existing types (that include deprecated member) in bold to make them more visible
In a previous post, I made available the WinmdDiff tool to list the new types in WinRT 8.1.
Today, my new DeprecatedApi tool will let you figure out what are the types and members that are deprecated in a version of WinRT. As shown in the following screenshot, the default path where the .winmd files are parsed is where the Windows 8.1 SDK stores the Windows.winmd file.
In the forthcoming versions of Windows, you will simply have to change this folder to get the new deprecated APIs of WinRT.
I hope this helps.
While I was on vacation, I prepared the next episode of our Windows Store Apps Development series has been published.
You’ll find demos, code and tools to help you write better Desktop applications with WinRT!
I’ve reviewed a nice article about debugging Windows Store Apps for Robert Evans, a collegue of mine at Microsoft with whom we publish video blog posts.
I’m pleased to announce that it is now available for your reading in the September issue of MSDN Magazine.
In a previous post, I explained how to use the WinRT API in Desktop applications with Visual Studio 2012 Release Candidate. I will soon provide an update for Visual Studio 2012 and 2013 on http://blogs.msdn.com/b/mspfe.
Meanwhile, you should start taking a look at the WinRT types that are usable by Desktop applications. For a given type, the MSDN documentation provides the list of supported platforms in the Requirements section at the end of its corresponding page
In order to help you, I’ve built a tool that directly lists the types recognized as usable by a Desktop App
There is no magic here: these types are decorated by an instance of DualApiPartitionAttribute. As the MSDN documentation states, it indicates that the type is supported in desktop apps and in Windows Store apps.
This is an approximation of the types we are interested in because some WinRT types are only available to Desktop Apps such as PackageManager used in my previous post. And in that case, it is not decorated by a DualApiPartitionAttribute. However, I’ve not found any other Destop-only type other than the types related to PackageManager such as PackageUserInformation or DeploymentResult.
I hope this helps
While I’m on vacation, the next episode of our Windows Store Apps Development series has been published.
As usual, you’ll find demos, code and tools to help you write better Windows Store Apps for your users!