# Simple.MahApps.Template

**Repository Path**: lanicon/Simple.MahApps.Template

## Basic Information

- **Project Name**: Simple.MahApps.Template
- **Description**: My opinion on how to do a modern enterprise ready WPF application (if people still do :))
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-03-28
- **Last Updated**: 2021-03-28

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

Simple.MahApps.Template
=======================

[![Build status](https://ci.appveyor.com/api/projects/status/l0e5oai0xdn7o4cc/branch/master?svg=true)](https://ci.appveyor.com/project/oriches/simple-mahapps-template)

As with all my 'important' stuff it builds using the amazing [AppVeyor](https://ci.appveyor.com/project/oriches/simple-mahapps-template).

The app is skinned using [Mah Apps](http://mahapps.com/).

This is my example of a templated WPF application using the MahApps control library to give a modern looking UI.

Okay this is *opinionated software* on the way to build a modern UI in WPF using MVVM as the MVC architecture and being 'pure' about the separation between the View & View Model, there are no UI concerns (colours, width's, control persistence) in the View Model (and never will be). If don't agree in full separation between the View & View Model then you might as well stop there :)

This test app makes use of node.js to create a mock backend server - it's not WCF or WebAPI :)

So if you're going to build this software make sure you have node.js installed and configured to build, I use VS2015 to build and test the node.js part, either by starting it from the command line 'node.js server.js' or by setting VS to start two projects at startup.

This app uses modern third party libraries for serialization, IoC, multithreading, it most definitely does not use PRISM or Unity :)


Happy coding...