title: Prevent Magic string with WPF Localization Extension
body: <p>I'm developing a WPF Application where the user is able to change the Language at runtime. In C# Code (ViewModels etc.) I'm using the reference to the resource.
  For example:</p>
  
  <pre><code>string translation = ScreenResources.WorkpieceDiameter;
  </code></pre>
  
  <p>This is supporting Intellisense and compile time errors. In XAML Code I'm using WPF Localization Extension:</p>
  
  <pre><code>Header="{lex:LocText xxxx.ScreenResources.WorkpieceDiameter}"
  </code></pre>
  
  <p>The Problem now is that in XAML Code I'm using a 'magic string', so if the resource name changes or move to another resource there wont be any compile time erros. Also the effort developing without intellisense member listing increases.</p>
  
  <p>Is it possible to use the resource with a static reference static like in C# Code without using the advantage of WPF Loc Extension?</p>