3) Load your project properties, and change the platform target from AnyCPU to x64 (or x86 if you’re on a 32 bit operating system).
Prerequisites / Limitations
You are obviously limited to WinRT-supported platforms: Windows 8 & 8.1, Windows Server 2012
Some of the WinRT libraries won’t work on the desktop platform, usually because they require a WinRT user interface. Pay attention to the MSDN docs which state whether they’re available for Desktop, but also feel free to experiment, as in some cases the docs are not accurate (for example, the Geolocation works on Desktop but the documentation states Windows Store apps only).
You might be surprised to know that WinRT can be used from Windows apps also, with a little bit of tweaking.
What is WinRT?
WinRT is not .NET or Win32, though it shares some similarities between both.
WinRT is an API over a new runtime, that supports platforms from Windows x86 to Windows Phone ARM.
WinRT is implemented in C++, but you can develop for it using C# and VB.NET.
Because the WinRT metadata is exposed as CLI metadata (in .WinMD files), you can reference and consume them from your CLR applications.
As a case study, we will look into changing the user lock screen to the Bing daily picture.
You will need to be reasonably comfortable with async code, as most of the API is exposed via Tasks.
Create a new Windows C# command line application:
I’ll call mine WinRTTest.
Referencing a WinRT library: Take 1
Now let’s try adding a reference to a WinRT library.
Go to Add Reference, and choose Browse:
Then hit the Browse button, and select C:\Program Files (x86)\Windows Kits\8.0\References\CommonConfiguration\Neutral\Windows.winmd (or the 8.1 version) and click OK.
Checking the documentation as instructed, we read this:
In the desktop projects, the Core subgroup doesn’t appear by default. You can add the Windows Runtime by opening the shortcut menu for the project node, choosing Unload Project, adding the following snippet, and re-opening the project (on the project node, choose Reload Project). When you invoke the Reference Manager dialog box, the Core subgroup appears.
Now reload the project and choose Add Reference… again. Suddenly, the Windows tab is available for us:
Let’s tick Windows and click OK.
Now let’s start coding with the WinRT libraries.
Adding the HttpClient NuGet package for downloading the Bing picture
The HttpClient class will be a nice easy way for us to use the Bing Daily Picture service.
First, add a reference to the NuGet package for the HttpClient.
In the Visual Studio menu, go to Tools > NuGet Package Manager > Package Manager Console
Then type in the following command at the prompt:Install-Package Microsoft.AspNet.WebApi.Client
Attempting to resolve dependency 'Newtonsoft.Json (≥ 6.0.4)'.
Installing 'Newtonsoft.Json 6.0.4'.
Successfully installed 'Newtonsoft.Json 6.0.4'.
Installing 'Microsoft.AspNet.WebApi.Client 5.2.2'.
You are downloading Microsoft.AspNet.WebApi.Client from Microsoft, the license agreement to which is available at <a href="http://www.microsoft.com/web/webpi/eula/net_library_eula_ENU.htm">http://www.microsoft.com/web/webpi/eula/net_library_eula_ENU.htm</a>. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Successfully installed 'Microsoft.AspNet.WebApi.Client 5.2.2'.
Adding 'Newtonsoft.Json 6.0.4' to WinRTTest.
Successfully added 'Newtonsoft.Json 6.0.4' to WinRTTest.
Adding 'Microsoft.AspNet.WebApi.Client 5.2.2' to WinRTTest.
Successfully added 'Microsoft.AspNet.WebApi.Client 5.2.2' to WinRTTest.
So now we have our new references:
Now, paste in the code below:
Note that we are hard-coded to get the 1080p version of the desktop, and there’s not much error handling. We’re keeping it nice and brief; getting the appropriate wallpaper size and error handling could be left as a future exercise.
David, your code sucks. It won’t compile.
I can’t argue with those statements:
1>------ Build started: Project: WinRTTest, Configuration: Debug Any CPU ------
1>C:\Projects\WinRTTest\WinRTTest\Program.cs(37,32,37,168): error CS4028: 'await' requires that the type 'Windows.Foundation.IAsyncOperation<Windows.Storage.StorageFile>' have a suitable GetAwaiter method. Are you missing a using directive for 'System'?
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
If you paid close attention to the MSDN docs earlier, it referred us to another page which states:
That said, your desktop app can’t consume much of anything from the Windows Runtime until you prepare your project with one essential reference. The Windows Runtime defines some standard classes and interfaces in System.Runtime, such as IEnumerable, that are used throughout the Windows Runtime libraries. By default, your managed desktop app won’t be able to find these types, and so you must manually reference System.Runtime before you can do anything meaningful with Windows Runtime classes.
While we could browse around for files, I believe it’s actually less error prone and simpler to reference the assembly name in our project file, and let Visual Studio do the rest. It also means you can prepare your project for WinRT in one edit of the project file (see the summary at the top of the article).
Now the System.Runtime reference isn’t going to be enough for us, as the async support extensions are in the WindowsRuntime classes. So add the following:
So we run the app. The image comes down and is saved into our Pictures folder as LockScreen.jpg:
But if you lock your machine by hitting Windows + L, our lock screen isn’t showing the changes.
Weirdly, it’s showing in the control panel though:
Well after some trial and error myself, let’s change the target platform from AnyCPU to x64 (or x86 if you’re on a 32 bit machine):
And it should suddenly work!
Now, it’s unclear why this is necessary (and why we see no errors, and the lock screen actually shows in the control panel). Frustratingly, I can’t troubleshoot the problem properly, as setting the platform target back to Any CPU suddenly continues to work also. There may be something else happening here; so I will update this article if an explanation ever comes to light.