Last time we finished with all the pieces except the common:MahAppsPopupWindowAction used in XAML. Prism already has a PopupWindowAction (it wasn't there a few years ago) so let's use that to create our own popup window action that will show MahApps-metro-style-dialog.

As you may know, there's a little problem with the attribute routing in ASP.NET MVC: generating a link (via Html.ActionLink) might get real slow when you've got hundreds of attributed actions. The answer to this issue is to use named routes, so instead of Html.ActionLink you use Html.RouteLink, but that's not quite handy, at least for me it isn't. Given that I'm used to T4MVC, it seems like a step back.

There are times that you need to call native (C/C++) code from .NET environment. To do so, you have several options: use C++/CLI, use P/Invoke mechanism, use some sort of inter-process communication like pipes, memory mapped files etc persuade yourself that it's gonna be easy to port this cool C/C++ library to C#. Shoot yourself in the head when trying to do it. We will discuss option 2.

Everybody knows you should be making backups of everything. Especially if it's your startup's database. Without db backup you'll probably be bald soon. And you don't want to be bald.