Going ny their commitment to ship new versions at a fast pace, Micosoft’s update to UWP Community Toolkit bring together a nuber of tools for developers to use in Windows 10 apps. This 1.2 version mainly focus on to stabilize current features while adding most missing one.
If you are a developer and want to get a first glance, you can install the UWP Community Toolkit Sample App directly from the Windows Store.
Here’s a quick preview features in this release:
- 7 new helpers to help with everyday tasks:
- BackgroundTaskHelper to help you work with background tasks
- HttpHelper to help you deal with HTTP requests in a secure and reliable way
- PrintHelper to help you print XAML controls
- DispacherHelper to help you work with tasks that need to run on UI thread
- DeepLinkHelper to simplify the management of your deep links
- WebViewExtensions to allow you to bind HTML content to your Webview
- SystemInformation to gather all system information into a single and unique class
- New controls named MasterDetailView that helps developers create master/detail user experiences
- ImageCache was improved to provide a more robust cache
- HeaderedTextBlock and PullToRefreshListView now accept ContentTemplate customization
- Facebook service now supports paging when requesting data
- Renamed BladeControl to BladeView, now also derives from ItemsControl, and allow more common convention like data binding and will make control aligned with SDK naming.
- For backward compatibility, previous control is kept and flagged as obsolete, so developers can still reference new version with everything working just fine. Microsoft notes, “obsolete classes will be kept until next major version before it removes.”
A compiler warning will be shown to encourage you to use the new version.
In other news, starting on February 14th, 2017, Microsoft Edge and Internet Explorer 11 will prevent sites that are protected with a SHA-1 certificate that chain to a Microsoft Trusted Root CA from loading and will display an invalid certificate warning, Microsoft stated today.
“Manually-installed enterprise or self-signed SHA-1 certificates will not be impacted, although we recommend for all customers to quickly migrate to SHA-256,” writes Microsoft.
For additional information on Microsoft’s overall SHA-1 deprecation plans, you can visit this TechNet.