Microsoft's UWP Community Toolkit hits version 2.0 with Fluent Design support, more

Microsoft initially introduced UWP Community Toolkit just over a year ago as a handy open-source resource for developing UWP apps. Now, after several smaller updates since launch, UWP Community Toolkit is moving to version 2.0 with the start of support for Microsoft's Fluent Design System and more.

The 2.0 release adds the necessary tools for developers to take advantage of new APIs in the Fall Creators Update. New and existing controls will also be updated over the coming months with support for the light, depth, material, motion and scale effects used in Fluent Design, Microsoft says. The sample app will be updated with a bit of Fluent Design as well to give developers something to tap for ideas.

In addition to the Fluent Design and API highlights, this release adds some new controls and updates others. From Microsoft:

  • Added InAppNotification control – a control to show local notifications in app
  • Added TextToolbar control – text editing control that enables easy rich text and Markdown formatting
  • Updated Expander to support all orientations and added LayoutTranformControl from the WinRT XAML Toolkit
  • Updated Menu to support underline characters, orientation and many other improvements

There are a whole lot more, smaller changes in the move to 2.0 to check out as well. For more, you can find the lengthy release notes at Microsoft.

UWP Community Toolkit on Github

Dan Thorp-Lancaster

Dan Thorp-Lancaster is the former Editor-in-Chief of Windows Central. He began working with Windows Central, Android Central, and iMore as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl

  • Wow, you're welcome for the tip... 2 days ago.
  • Where did you send the tip? I scour the tips inbox every day and I don't remember reading yours. :o
  • Used the WC app to email all the deets with screenshots and all. Sent 8/29 12:22am (eastern time)
  • If only developers were interested in UWP
  • Why downvotes? When he said that, basically he means majority of developers do not interest in UWP. At least for now. Even Spotify which available at the Store is actually non-UWP version.
  • After wrapping it, it's not a win32 either... People care or not...
    Just curious, which is more applicable for new startups / freshmen?
    1. code a win32 application then wrap it?
    2. code uwp.pc SKU? (runs on win10, win10s, win10.arm)
    3. code win32 and implement your own mechanism to install, update, crack-proof, advertisement, refund, etc? Can I trust a random no body's win32 app? Can I trust you to clean up your mess (registry) during uninstallation? It's another story if you have a lotta legacy stuff (or working in a big firm), it's not like you can ignore it (UWP)... If you want code for Xboxes... SKU is your choice.
    uwp.iot SKU? uwp.AR/MR SKU? SKU is indeed dead imo... (people are busy enuf wz 2 other OS already)