December 2014 Entries

I recently had cause to reference two libraries which both contained the same class file. The Namespace : Class where therefore ambiguous within my application. Interestingly enough the .Net compiler simply takes it’s bat and ball home and does not allow you to access any of the exported types from these assemblies.

To resolve this you need to create an alias for at least one of the dlls. You do this in the Reference Properties:

  1. Add references in your app to the dlls.
  2. Right click on one of the assembly entries in the References list and click Properties.
  3. In the properties windows you will see an ‘Aliases’ property with the value of ‘global’. Change this to be ‘global, myalias’.

Click build and everything should be OK except when you try to use the ambiguous class. I.e. the .Net compiler will now be happy about the scope of all of the other exported items.

To use the actual ambiguous class you need to add an extern alias:

namespace MyApp
    extern alias myalias;
    public class MyClass
        var myClass = new myalias::AmbiguousNamespace.AmbiguousClass();

Note: you could prefix every declaration using the ‘global::’ scope, but that is the default so we don’t need to bother.