So with this blog post we’re starting a new “Microsoft Store Open Source Series”, where we will go through examples of these APIs and libraries we built for the Microsoft Store. AsyncRela圜ommand and other MVVM Toolkit improvements.We’ve already open sourced several features that were first implemented for the Microsoft Store, like: Because everyone in our team loves open source software, and thanks to our close collaboration with the CommunityToolkit teams, we’re also always looking into ways to make all these new bits of functionality public, so that everyone in the community can leverage them in their own applications as well. In doing so, we often find ourselves building some new libraries or APIs that we can then reuse in the rest of the application. While working on the Microsoft Store, we’re constantly pushing the boundaries of what native app development on Windows can do. With this new series, we want to try something new.
But of course, we could only share some very small bits of our actual code, as the Microsoft Store app itself is not open source. NET concepts and explain how we solved some problems while working on the app. In our previous blog posts, we used the Microsoft Store itself as a case study to introduce general. This is part of our new “Microsoft Store Open Source Series” of blog posts, expanding on our prior posts about the new Microsoft Store for Windows - reducing binary size with trimming, and migrating from C++/WinRT to C#. Plus, we have a new source generator which makes using app services a piece of cake! □ Looking for ways to empower your UWP app beyond what you thought was possible? Today, we’re going to show you how to leverage the AppServices library we built for the Microsoft Store to unlock the power of Win32 APIs.