class name conflict from different dlls

Mrudul Ganpule

12y1.8kC#

I am using two dlls XeroApi.dll and DevDefined.OAuth.dll both have OAuth class , problem is that i have used OAuth class of XeroApi.dll earlier in my project. Now i am trying to use this OAuth class from DevDefined.OAuth.dll, then it is giving error that OAuth is present in both dll , it is conflicting

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes12y ago
If it's not working then you must be doing something wrong such as leaving in the 'generic' using directive.

For example, the following code compiles and runs fine until you uncomment:

using N2;

You then get the 'ambiguity' error.

using N1;
//using N2;
using A2 = N2.A;

namespace N1
{
class A
{
}
}

namespace N2
{
class A
{
}
}

class Program
{
static void Main()
{
A a = new A();
}
}

It won't help if you put one of the dlls in the GAC since this won't affect the names of the classes in that dll.
Mrudul Ganpule12y ago
still i got same problem, can we resolved by this using GAC with strong name of file to avoid version conflicts? but dll names are different.

If possible , then how?
Vulpes12y ago
If you don't want to interfere with the code you've already written and only want to access one class from DevDefined.OAuth.dll, then you could do it using a type alias.

In other words, replace your generic using directive:

using DevDefined.OAuth; // if that's the actual namespace

with:

using OAth2 = DevDefined.OAuth.OAuth;

You'd then need to use Oath2 whenever you want to refer to Oath in this particular dll.

If you want to access a few other classes in the same dll, then you could define aliases for each of them which could just be the class name itself if there's no conflict.

However, if you need to access a lot of classes in that dll, then this approach is impractical and it would therefore be better to use fully qualified type names whenever you need to use the Oath class even if you have to change existing code.