Show Metro Dialog Async(new Custom Base Metro Dialog()); // create and show custom dialog with own settings await this.Please note that everything that is know deprecated will be removed in the 1.0 release, so you should prepare your applications soon.Since we’re following semantic versioning, we promise to not break anything from version 1.0 to 2.0. Metro now allows to define custom themes for the application.My changes and additions were not making their way into the UI display.No matter how many times I invalidated the User Interface it just would not get displayed.There are three kinds of version compatibility testing we do: (1) binary compatibility, (2) source compatibility, and (3) serialization compatibility. You may also find these approaches useful in your testing, and should an issue arise this may help you narrow down the root cause. Strong naming Mah Apps will no longer be strong-named beginning with this version. Strong-named assemblies are only useful in some rare scenarios.If you need strong-named assembly then you can compile the source by yourself ore use the Strong Namer from Daniel Plaisted @dsplaisted or Strong-Name Signer from Werner van Deventer @brutaldev.Show Metro Dialog Async(new Custom Base Metro Dialog(this.metro Dialog Settings)); // or await this.Show Metro Dialog Async(new Custom Base Metro Dialog(this, this.metro Dialog Settings)); This is the first stable release of Mah Apps. We removed everything marked as obsolete and made some API changes, but from now on Mah Apps.