title: Ambiguous reference between MonoGame & Microsoft.XNA.Framework namespaces
body: <p>MonoGame (a framework which basically brings XNA to Windows Phone 8) has all it's namespaces prefixed with <code>Microsoft.Xna.Framework</code> I believe to minimise the amount of code changes required when porting your XNA app to MonoGame.</p>
  
  <p>My issue is, I wish to access the <code>Microphone</code> class, which, because has not been created in MonoGame yet, I have to utilize it from within in the official Microsoft XNA class, this requires taking out the explicit forced removal of the standard <code>Microsoft.XNA.Framework.dll</code> references within the .csproj that my MonoGame template has setup to avoid conflicts, which works great and now <code>Microphone</code> is accessible, but in doing so I have created ambiguity between a few key classes which both exist in Microsoft standard issue and MonoGame.</p>
  
  <p>The errors I am receiving are:</p>
  
  <blockquote>
    <p>Ambiguous reference: <br/>
    Microsoft.Xna.Framework.Color<br/>
    Microsoft.Xna.Framework.Color</p>
  </blockquote>
  
  <p>This has obviously occurred because alongside the standard Microsoft-issued XNA library, I have a reference to <code>MonoGame.Framework.dll</code> which commandeers the namespace, creating this ambiguity. However, in all instances, I wish to access the MonoGame version.</p>
  
  <p>Any ideas how I can explicitly tell the compiler to use the MonoGame version of the <code>Color</code> and <code>Vector2</code> class and not the official Microsoft one?</p>
  
  <p>Any attempt in a <code>using Color = Microsoft.Xna.Framework</code> obviously won't work because they are both labelled the same in the compiled dlls!</p>