Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- A typical folder structure for a WPF (Windows Presentation Foundation) application could look like this:
- MyWpfApplication (Solution Folder)
- ├── MyWpfApplication (WPF Project)
- │ ├── App.xaml
- │ ├── MainWindow.xaml
- │ ├── Properties
- │ ├── Resources
- │ ├── App.config
- │ └── ...
- ├── ViewModel (Class Library)
- │ ├── MainViewModel.cs
- │ └── ...
- ├── Model (Class Library)
- │ ├── MyModel.cs
- │ └── ...
- ├── Services (Class Library)
- │ ├── DataService.cs
- │ └── ...
- ├── Tests (Unit Testing Project)
- │ └── ...
- └── MyWpfApplication.sln
- MyWpfApplication (WPF Project): This is the WPF project housing your application. It should include XAML files for your UI, such as App.xaml and MainWindow.xaml.
- ViewModel (Class Library): This is where your ViewModels go, following the MVVM (Model-View-ViewModel) pattern. They are essentially the logic behind the UI, the bridge between the Model and the View.
- Model (Class Library): This is where your Models go in the MVVM pattern. These are typically representations of the objects you'll be working with.
- Services (Class Library): This project typically houses various services the app may need, such as Data Services, APIs, etc.
- Tests (Unit Testing Project): This is where your unit tests would go, to ensure that methods and classes work as expected.
- Please note that you could use JetBrains Rider for working with WPF applications and benefit from its robust code analysis, intelligent code completion, real-time type-checking, and powerful refactoring capabilities.
Add Comment
Please, Sign In to add comment