There are plenty of ways to test web apps, but most of them require a cumbersome setup and a lot of tools installed and I’m just too lazy to do that. But I just found something that may work in my favour.
First there was ASP.NET Membership (well, maybe not first, but it was released a long time ago), then there was the ASP.NET Simple Membership, then ASP.NET Universal Providers now there’s the “latest and greatest” ™ ASP.NET Identity. Let’s dig in.
A time ago I wrote about using collection views in WPF to achieve different looks at the same source collection. By creating different instances of ListCollectionView we could have the collection displayed in different sorting, ordering and grouping shape. Unfortunately there is small trap when using collection views.
Until recently, creating a custom window style in Windows Presentation Foundation was quite a challenging task. You had to implement the window’s behavior from scratch. Resizing, moving and all other typically window related functionality had to be reinvented and reimplemented just because you wanted the window header bar to look different.
WPF has many rich features which facilitates making a great look&feel of the application. Unfortunately many of those features are cumbersome to implement and use when we develop in a Model - View – ViewModel architecture. In this post I will try to make you more familiar with visual states and how can we use them in our MvvM application.