For localization I\'m using the Resource-file (.resx files) functionality in .NET, but I\'m wondering if there\'s a smart way to databind the various localization properties
Very similar to what Geek proposed, but even a bit easier I think:
Create a class in the same assembly, which inherits the resources file and exposes a public constructor, then use this class instead.
public class ResourcesProxy : Properties.Resources
{
///
/// resolves the problem of internal constructor in resources.designer.cs
/// in conjunction with xaml usage
///
public ResourcesProxy() : base()
{
}
}