the gist

In order to target some framework packages in Visual Studio 2017 RC, you should ensure that you have the latest Windows Insider Preview release installed. This will require that you participate in the Windows Insider Program, which is Microsoft's platform for distributing pre-release versions of Windows 10 and the accompanying .NET Framework SDK's. So head over to the Windows Insider site, sign-in, and follow the steps outlined on the page, which as of this writing are below.


Windows Insider Preview Download Page

Again, your workstation should have the latest Windows 10 Insider Preview release installed. As it reads on the site, the team automatically matches the latest Windows 10 SDK and Windows 10 Mobile Emulator preview releases to the build for you. This is far more convenient than it sounds.

Once the Insider Preview Release build is installed, you should be able to create Windows Universal projects using Visual Studio 2017 RC.

Also, note the important disclaimer regarding Windows Store access. In essence, any applications submitted to the Windows Store that have been built using the pre-release SDK will be rejected.

That said, you may wish to fall back to targeting the .NET Framework 4.6.1 or the .NET Framework 4.5 packages and/or simply use Visual Studio 2015 altogether if you are working on a Windows Store app.

The long story.

In attempting to load a new Universal Class Library in Visual Studio 2017, I was presented with this error:


Error dialogue in Visual Studio 2017 RC

No solutions available.

After a searching the world wide knowledge base, and not finding a solution, I began to run through the process of elimination. The project was targeting .NET Framework version 4.6.2. So I needed to confirm that I indeed had the framework installed.
After launching the Visual Studio installer, and clicking on the Individual Components tab, I found that indeed, the .NET Framework 4.6.2 SDK and .NET Framework 4.6.2 targeting pack both were unchecked. So I checked the boxes and proceeded with the update.

Still no luck.

Upon completion, I launched Visual Studio again and attempted to create a new Universal Windows project. Again, I was presented with the same error, No suitable SDK to target. Now what gives? The only possible issue can be a different "version” of the SDK being available. So I proceeded to search the world wide knowledge base again for Windows 10 SDK's and .NET Framework SDK's and followed the breadcrumbs to this Windows 10 blog post. What I found interesting was that the latest version of the SDK and targeting pack requires Visual Studio 2017 (and obviously vice versa). Also, my workstation should have the latest Windows Insider Preview release installed.


Things to note: The SDK will require Visual Studio 2017 Preview. You can download the Visual Studio 2017 Release Candidate here.

Windows 10 Insider Preview release required.

The first step on the page is to Install the latest Windows 10 Insider Preview release. After reading this, I needed to check my current Windows 10 build, which was not an Insider Preview.


Given that I already participate in the Insider Program, I needed only to switch on Insider Preview builds for this workstation.


So I proceeded to the Action Center > All Settings > Update and Security > Windows Insider Program and clicked Get Started. Then I sat back and allowed the device enrollment and installs to proceed.


Because I would like for this workstation to remain somewhat stable for on-going development, I opted for the Slow Insider Level.

All set to go.

Having installed the latest Insider Preview build, which brought with it the accompanying SDK's I was set. I launched Visual Studio 2017 and proceeded to create a new Universal Windows project and was presented with this dialogue:


You will easily note that you can't target a build that is higher than that which is installed on your workstation, yet you can choose a minimum version as low as the initial release of Windows 10.

If you're unsure of which versions to choose, click the link Which version should I choose? which will take you to a page that will define the differences in the various versions which should help you to choose the correct versions for your project.


Comments are closed