WPF DataBinding Overview

I quick review of how WPF binding works can be found here. Basically the MSDN documents but very informative.

Deserialization Problems

I had a problem: The constructor to deserialize an object of type was not found. Seems the solution might be simple enough.

Stored proc are bad, m'kay

I hate stored procedures and personally do not use them, but this article really gives valid points to my preference of not using them at all.

Sending key presses to controls in WPF

The easiest way is to do the following:

KeyEventArgs keyEventArgs = new KeyEventArgs(e.KeyboardDevice, e.InputSource, e.Timestamp, Key.Right);
keyEventArgs.RoutedEvent = e.RoutedEvent;
.RaiseEvent(keyEventArgs);

Because of security restrictions, the type {custom type} cannot be accessed

Had the unfortunate priviledge of encountering this message when using remoting. The solution was quite simple at least.

Just add:
[assembly: AllowPartiallyTrustedCallers]

This solved the whole problem. The whole problem was in my case that my assembly was signed and it lived in the GAC. It is a framework assembly so it must be signed and must live in the GAC.

Performance Counters

A quick and dirty way to add performance counters to your application.

Namespace problem in XAML

I had to do some changes to my XAML forms, and decided to use XmlDocument or DOM for it. The DOM works great when only updating existing elements but when adding new elements it insists on adding the xmlns="..." attribute to all my new elements.

Unfortunately according to this conversation it is the way it is, so I was forced to massage the xml using standard string parsing just after XmlDocument serialized my XAML form.