Windows 10 SDK Preview Build 16288 and Mobile Emulator Build 15240 Released

[Cat']

Today, we released a new Windows 10 Preview Build of the SDK and the Mobile Emulator to be used in conjunction with Windows 10 Insider Preview (Build 16288 or greater). The Preview SDK Build 16288 contains bug fixes and under development changes to the API surface area.

 

The Preview SDK and Mobile Emulator can be downloaded from developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum. For new developer feature requests, head over to our Windows Platform UserVoice.

 

Things to note:

• This build works in conjunction with previously released SDKs and Visual Studio 2017.  You can install this SDK and still also continue to submit your apps that target Windows 10 Creators build or earlier to the Store.
• The Windows SDK will now formally only be supported by Visual Studio 2017 and greater. You can download the Visual Studio 2017 here.

Breaking Changes

• ecmangen.exe removal from the SDK:  Ecmangen.exe will no longer ship with the Windows SDK. Developers who rely on ecmangen for event manifest creation are advised to install the Windows Creators Edition of the SDK to obtain the file. Developers may also use notepad or other XML editor of choice for manifest creation. A schema file is available on MSDN to aid in manifest creation, for tools that support it.

API Updates and Additions

When targeting new APIs, consider writing your app to be adaptive in order to run correctly on the widest number of Windows 10 devices. Please see Dynamically detecting features with API contracts (10 by 10) for more information. 

There have been no changes since build 16278 to the API surface.

 

Article:

https://blogs.windows.com/buildingapps/2017/09/19/windows-10-sdk-preview-build-16288-mobile-emulator-build-15240-released/

[D1v1n3DC]

Current slow ring build is 16288.1 while showing up as winver 1709 and it is running extremely smooth on this system I am typing on. With uBlock Origin working in Edge extension to block all toms hardware ad crap and videos ads, had a little issue with build 16278 which is current ISO build from MS. I did find that in 16288.1 that it uses a lot more ram in Edge browser I am up to 613Mb just one tab right now as you can see in the image, but seems to be climbing must be a memory leak with edge. So looking into the process running under the edge tab the largest memory use is extension so memory leak with ublock in current builds hopefully fixed soon.