You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone, I am trying to set up an infrastructure for a user login system and menu authorization. I am doing research to rewrite my current CRM project with Windows App SDK (WinUI 3). I want to use MVVM pattern and aim to keep my dependencies to a minimum. I have some experience with UWP and WPF in the past.
I am examining the "VanArsdel Inventory" UWP application from Microsoft sample projects. As far as I understand, they created the MVVM pattern themselves in this project. They did not use a framework. This is quite difficult for me to understand. I understand that there is an architecture that revolves between App.xaml, SplashScreen, ShellView, NavigationView pages. I understand that this is what should be in a CRM project.
If I come to what I want to ask; Is there a Microsoft best practice for Login and Navigation authorizations?
The text was updated successfully, but these errors were encountered:
My research continues; and I came across an application like Inventory in the repos. SceneGraph (WindowsCompositionSamples). Will this application continue to be developed? Will a structure that includes a SQL Server connection and Login infrastructure like in UWP be used?
Hi everyone, I am trying to set up an infrastructure for a user login system and menu authorization. I am doing research to rewrite my current CRM project with Windows App SDK (WinUI 3). I want to use MVVM pattern and aim to keep my dependencies to a minimum. I have some experience with UWP and WPF in the past.
I am examining the "VanArsdel Inventory" UWP application from Microsoft sample projects. As far as I understand, they created the MVVM pattern themselves in this project. They did not use a framework. This is quite difficult for me to understand. I understand that there is an architecture that revolves between App.xaml, SplashScreen, ShellView, NavigationView pages. I understand that this is what should be in a CRM project.
If I come to what I want to ask; Is there a Microsoft best practice for Login and Navigation authorizations?
The text was updated successfully, but these errors were encountered: