A couple of years in the past we created a code pattern for enterprise builders referred to as Buyer Orders Database, designed to display how builders can create and handle buyer accounts, orders, and merchandise for the fictional firm Contoso.
It was highly regarded, so we continued updating it to assist every new model of Home windows and the Home windows App SDK, and to display present design steerage. Final 12 months we up to date it to make use of WinUI 2.6.
In Could of this 12 months, simply in time for Microsoft Construct, we gave it a serious overhaul to work with Home windows App SDK, and to assist the most recent Azure options. After all, we needed to make it have a look at house on Home windows 11. So now, based mostly on WinUI 3, the Buyer Order Database showcases UI controls together with a knowledge grid from the Home windows Group Toolkit.
Making use of Azure Energetic Listing (AAD) authentication, Sqlite and SQL Azure database integration, the Entity Framework, and cloud API companies.
We hope that is only the start for the Buyer Orders Database code pattern, and we’d like your assist making future variations even higher.
So we’re asking you, what else ought to the pattern do?
What different options would you just like the pattern to incorporate? What’s stopping you from utilizing it as the premise for a challenge in your enterprise? Tell us what you assume in order that we will begin including options and bettering our documentation to fulfill the communities’ particular desires and wishes. Our objective is that can assist you create a strong app, constructed utilizing present finest practices, that you should use as a basis on your personal tasks. On the very least, you possibly can study the code and see the way it’s performed.
Share your suggestions with [email protected] and we’ll comply with up with one other weblog put up when we have now the following replace of the pattern.
Thanks!
John Kennedy, Senior Content material Supervisor, Home windows Developer Documentation
