Replies: 2 comments
-
I'm usually starting out with a "WinUI 3 app with packaging project" using the Visual Studio "File > New Project" dialog. If I know I'll add more projects later (e.g. tests), I then move the project into a src folder since I really like David Fowlers suggested project structure. After that I start copying CI/CD files from another projects into the project if I need it (because they were difficult to get right and there isn't much documentation on this) and then also setup a separate package identity for debug builds to prevent name clashes between local version and deployed versions. Once I'm done with that, it's "just" developing the app. In the past I've also used Windows Template Studio in the past, but it often felt overkill or too opinionated and also didn't follow the project structure I prefer nor did it add unit test projects. |
Beta Was this translation helpful? Give feedback.
-
i have my own Project Template and Wizard, i know that there is a Template Studio, but it is very confusing and heavy, so i created my own Wizard. When the project is created, everything is ready, such as title bar, theme service, settings Page and more... |
Beta Was this translation helpful? Give feedback.
-
Hey everyone! I'm wanting to understand the WASDK developer journey better, starting with the OOBE (Out Of Box Experience). When you want to start building a Windows App, where do you start?
Beta Was this translation helpful? Give feedback.
All reactions