title: Hook the resolution of assemblies and types loaded in a Xaml context
body: <p>for a good reason we are <strong>prefixing</strong> our assemblies, with a <strong>prefix specific to each application</strong> :</p>
  
  <p>e.g. if we have a project named "A" which is a dependency of an application named "MyApplication1" the latest will use a "MA1.A" assembly generated at build-time;</p>
  
  <p>if another application "MyApplication2" has also a dependency on "A" we will transform the output of "A" as "MA2.A" when building the application...</p>
  
  <p>So far so good.</p>
  
  <p>Now we are starting to use <strong>WPF</strong> and we need to <strong>reference some types of "A" in the Xaml</strong> :</p>
  
  <pre><code>xmlns:a="clr-namespace:Some.Name.Space;assembly=A"
  </code></pre>
  
  <p>This is fine at design-time but at runtime there is no more "A" assembly but a "MA1.A" or "MA2.A" assembly,
  so the application crashes.</p>
  
  <p><strong>Do you have any idea to workaround this issue without affecting too deeply the development process ?</strong></p>
  
  <p>E.g. loading the Xaml by hand and setting the prefix is not an acceptable solution.</p>
  
  <p>Thanks in advance for any idea.</p>