Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

When UWP Apps Targeting Old or Temporary SDKs Can't Be Loaded [Code Snippet]

DZone's Guide to

When UWP Apps Targeting Old or Temporary SDKs Can't Be Loaded [Code Snippet]

In reviewing some UWP functionality, the author tried to open an old test project from earlier this year. Read on to see what happened.

· Mobile Zone ·
Free Resource
All this month, I'm taking some time each day to explore (and document) things that are related to UWP development that I haven't fully investigated or used before. While doing it over lunch each day I'm calling it #UWPLunch.

In reviewing some UWP functionality I tried to open an old test project from earlier this year. It was a project to test some of the functionality announced at build this year. The functionality was made available at the time via a special SDK (version 14295) that wasn't an official/formal release.

When trying to open that project on my recently rebuilt PC, solution explorer shows that an update is required to load the project. Trying to download the update presents a dialog like this.

There's a problem with the install link, though. It doesn't go to an SDK to download as there isn't one.
The solution was to manually modify the csproj file.
Above you can see that I've changed the TargetPlatformVersion to be the latest (AU) version and now the project can be loaded.

Ok, so this isn't something everyone will need but if you ever find yourself with an old project you can't open or get something someone has shared online and it won't open then this may help you out.
Topics:
development ,sdk ,functionality ,uwp

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}