Build your own apps with UWP Community Toolkit – Checklist Mag


Pay $0.002 per click to your site! Join now: Click Banner

Build your own apps with UWP Community Toolkit

The UWP Community Toolkit unites various apparatuses for engineers to use in building up their own particular Windows 10 applications. It’s a fairly specialized subject, thus if aide capacities, custom controls, and application administrations don’t mean anything to you, then you likely won’t be excessively amped up for the arrival of UWP Community Toolkit 1.2.

On the off chance that you are an engineer sort who gets this stuff, then you’ll likely be glad to see it. This is what you can expect in the overhauled form:

The focus of this version was to stabilize current features while adding the most wanted ones that were missing. A full list of features and changes is available in the release notes. Here’s a quick preview:

  • New Helpers. we worked on providing 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

    • We introduced a new control named MasterDetailView that helps developers create master/detail user experiences
  • Updates. We updated the following features:

    • 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. BladeView now also derives from ItemsControl. This will allow for more common convention like data binding and will make the control aligned with SDK naming. To guarantee backward compatibility, we kept the previous control and flagged it as obsolete. This way, developers can still reference the new version and everything will work just fine. A compiler warning will just encourage you to use the new version. The current plan is to keep obsolete classes until next major version and then remove them.


Be The First To Get TECH Updates. Enter your email address:

Delivered by FeedBurner


Can’t find what you’re looking for? GOOGLE IT!


Leave a Reply