![]() (The Android SDK is on the same schedule, but has to be updated separately, and outside of VS (by running the SDK Manager as Administrator).) Because I had the Preview Windows 10 SDK initially installed, to play it safe, when the final Windows 10 SDK came out, I blanked Baby Pavilion and did a complete reinstall of everything (every SDK, soup to nuts), and do every-other-week updates of VS and the Windows/Azure SDKs from within VS. And the Windows 10 SDK that was available when 10 was release was NOT the final SDK, but still the Preview SDK - that was posted here on Neowin, in fact. What I had to do was install the SDK while VS Community was closed (the same applies with the Azure SDK) - some updates must be initially installed while Visual Studio is closed - this also applies to some updates. I have ALL the SDKs on Baby Pavilion (including Windows 10). ![]() The problem I had with community is that when I tried it (when w10 was released) it was completely screwing up, things didn't get installed, changing features would remove features I couldn't get back and it refused to work with the windows 10 SDK at all, not sure if the recent updates have fixed things but the enterprise edition installed fine and didn't have these issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |