Recently I had to build a very dynamic DataGrid in WPF, in which the columns were constructed dynamically. And some rows did not contain data for each generated column. I stored the dynamic values in a dictionary and bound the dynamic columns to the indexer property. The problem was that the dictionary throw an KeyNotFoundException… Read More »
Back to: F# Journey: Course 2- Type Inference The concept of a function exists is in F# too. However, it’s slightly different than in C#. A F# function has a name, list of parameters and a return value. The function itself is assigned to a value with the “let” keyword. The parameter types are inferred… Read More »
Back to: F# Journey: Course 1 – Immutable Values You probably know type inference already from C#. But in F# it’s like magic! You don’t have to define the type quite often. The compiler will automatically find out. Let’s start with some examples: let a = 1 // or let plus a b = a… Read More »
After working 4-5 years mainly with object-oriented programming languages like C#, I thought it’s a good time to dive into other programming paradigms. For example: Functional programming -> F#! Based on the “Indeed Trends” (see at the bottom of this post) we see that the market is still not seeking a lot F# or Scala… Read More »
Back to: F# Journey By default all variables in F# are immutable. Hence.. we can not call them “variables” anymore. The term “value” fits better. Here is a simple example of an immutable value: let val1 = 2 printfn "%d" val1 Now when you try to change the value like in the code below (line… Read More »
Every .NET developer has already used an Ambient Context without knowing it. A typical Ambient Context is: using (var tx = new TransactionScope()) { …. } The pattern is not very well known. Here is one good description I found: The Wandering Glitch – Ambient Context I found this pattern very useful for displaying progress/busy… Read More »
In one of my projects (WPF, WCF) we are working with server and client side entities. Although the entities look very similar, we had some reasons to separate them: – Client side entities require more logic -> Implementation of INotifyPropertyChanged -> Implementation of IEditableObject -> Restore handling (When user cancels edit) All these functionalities were… Read More »
Data Annotations provide a very nice way to validate the entities. But under some circumstances, you may don’t want to validate all properties. For example, a property like “createddate” we don’t want to validate in the client layer, because the field is not set at this point. In this situation it would be good to… Read More »
I wrote a very tiny MVC Application Framework which runs on OWIN. This Framework uses the Razor engine for the view rendering. It’s very fast because the overhead is quite small. There are just a few lines of code which are between the Owin HTTP server request and the application logic. For that it doesn’t… Read More »
The Razor engine can be used outside of ASP.NET. Beside the cool syntax, it’s a very fast engine! And it’s quite easy to use. In my example I generate a XML file based on a razor template. (You have to install the NuGet package “RazorEngine”. This is my model which I use for the rendering:… Read More »