We’ve been using semantic versioning for a while now and it’s been paying out. Though there were some ‘quirks’. Now, version 2.0 is (almost) out and guess what, it addresses them! Let’s take a look at the new version and see what changed.
Recently I faced the problem with deploying an WPF application, which uses Entity Framework and Sql Server Compact 4.0 nuget packages. The application was deployed automatically by TFS Server as a Click Once installer. The problem was that the setup did not download Sql Server package at client machine and application could not work. Apart from checking what is maybe wrong on TFS side configuration, the simplest solution was to do a so called Private Deploy of the Sql CE libraries. Unfortunately it turned out to not be easy too.
In a previous post I showed you how to use IDataErrorInfo interface to implement simple validation mechanism in WPF MvvM application. In this post we will try to extend and customize this approach a little.
Windows Presentation Foundation allows us to create our own value converters and use them in XAML bindings. WPF also comes with a set of predefined converters. One of them is BooleanToVisibilityConverter. It this post I will show you how to create own version of this converter with parameter feature supported.
Have you ever straggled with generating and polishing gradient for wpf in xaml? I did many times. Did you use any tool for that, except Visual Studio Property tab? I didn’t. Until I stumble upon Online Gradient Maker.
I wanted to have a reusable email validator since there have been a few cases already where I needed one. Previously I just used the RegularExpressionAttribute but that’s verbose for email. So, without thinking much, I created an attribute that derived from RegularExpressionAttribute and supplied it with a regex I used – that turned out to be a surprise.