WPF Design patterns
Hey!
I was wondering, how is the WPF solution structured? How detailed should it be separeted in multiple projects? Is it similar to APIs or something? So "WPF project" (views, viewmodels), "application project" (services, models), "Data project" (working with db), etc?
5 Replies
$itdepends
I've personally never split the application into 3 libraries. Maybe 2 (a dll and a thin wrapper exe) to allow unit testing, but I've never seen any point in arbitrarily introducing more projects
ah okay. So this multilayer architecture is more of a web application thing? (or you dont split app there as well?)
Multilayer architecture is still a thing, but why use multiple projects instead of just different namespaces?