title: WPF control throwing 'resource identified by the URI missing' exception
body: <p>On loading the plugin and trying to create 'XYZ' control, the application throws the following exception:</p>
  
  <blockquote>
    <p>"The component 'XYZ' does not have a
    resource identified by the URI
    '/ThePluginAssembly;component/XYZ.xaml'"
    on the InitializeComponent() method in
    the UserControls constructor.</p>
  </blockquote>
  
  <p>The key points are:</p>
  
  <ol>
  <li><p>The user control is located in the plugin assembly</p></li>
  <li><p>I am trying to create the usercontrol from inside the plugin assembly</p></li>
  <li><p>The plugins are located in the same directory as the main application</p></li>
  <li><p>The user controls only have problems when they are created through XAML. I have a couple of other usercontrols in the same assembly but I instantiate these using code. I only receive the error message when I attempt to create a UserControl in XAML.</p></li>
  </ol>
  
  <p>On doing some google, i realized that this happens when two instances of my plugin are loaded in the application. When i removed my plugin from one of the folders ( I allow this plugin to be loaded from two locations) this exception stopped recurring.</p>
  
  <p>My questions:</p>
  
  <p>1) What is the reason behind WPF trying to resolve a URI to load my control?</p>
  
  <p>2) Isn't there a way by which i could have two instances of my plugin loaded in the application and somehow get rid of this exception? or some way to create a unique URI for each instances (if this exception is caused by a conflicting URI).</p>
  
  <p>Any comment or reference would be of help.</p>
  
  <p>Thanks for your interest.</p>
  
  <p>Edit:
  Same problem as posted by Phil : <a href="https://stackoverflow.com/questions/1453107/how-to-force-wpf-to-use-resource-uris-that-use-assembly-strong-name-argh">How to force WPF to use resource URIs that use assembly strong name? Argh!</a></p>