Problem regarding confilcting Class names

Question

0.00/5 (No votes)

See more:

Hello All,

I am facing a problem where I have 2 classes residing in discrete namespaces with the same name and same method signatures. This is a 3rd party DLL so I cannot modify them to use a common base class, or implement an interface. I want to create object of that class and use in my application.
I'll give you an example.

namespace A
{
   public class ABC
   {
      public void DoSomething()
      {
         MessageBox.Show("ABC of A");
      }
   }
}

namespace B
{
   public class ABC
   {
      public void DoSomething()
      {
         MessageBox.Show("ABC of B");
      }
   }
}

Now, my problem is, i want to create an object of ABC class based on some logic to choose from which namespace. So, is it necessary that i create separate objects for both classes and then use in my application?
I tried this :

object obj;
if(somecondition)
{
   A.ABC objABC = new A.ABC();
   obj = (A.ABC)objABC;
}
else
{
   B.ABC objABC = new B.ABC();
   obj = (B.ABC)objABC;
}

but "obj" doesn't get that DoSomething() method.
My appl'n methods use that ABC object and i don't want to overload each and every method.
Is there a some way by which i can define common object and use it in my methods without overloading them?

Thanks

Posted 9-May-10 20:35pm

nagendrathecoder

Updated 9-May-10 23:11pm

Pete O'Hanlon

v2

Add a Solution

5 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2010-05-09T22:49:00

Solution 2

Based on your reply to Josh_Jackson, I'd suggest that you use an interface to constrain both types. If they are completely different functionality, but share the same public contract then you can instantiate from the interface:

public interface IFoo
{
  void DoSomething();
}

public class Foo : IFoo
{
  public void DoSomething()
  {
    Console.WriteLine("Foo");
  }
}

public class Bar : IFoo
{
  public void DoSomething()
  {
    Console.WriteLine("Foo");
  }
}

Then, you can use this by referencing the interface as the type (and instantiating it with the concrete implementation):

IFoo instance = null;
if (somecondition)
{
  instance = new Foo();
}
else
{
  instance = new Bar();
}
instance.DoSomething();

Posted 9-May-10 22:49pm

Pete O'Hanlon

Comments

nagendrathecoder 10-May-10 5:06am

Actually, these 2 namespaces resides in two different versions of dlls of a third party product.
I want my appl'n to work on both versions of that product.
But for that to achieve, i have to create 2 different objects of same class in two different namespaces and also have to overload my all methods.
I wanted some way to create object so as i don't need to overload my all methods.

I tried your method but still with that too, i have to create 2 different objects as i can't modify thrid party dlls.

Pete O'Hanlon 10-May-10 5:09am

You could have told us this information in your original post. Please, we can't read your mind, and this is highly pertinent information. When you pose a question, you must give all the detail needed to answer otherwise people will not be able to answer properly.

nagendrathecoder 10-May-10 5:16am

I understand that and i apologize for that.
Is there any way to achieve what i need?
It'll save loads of work for me.

Joshua Tully · Answer 2 · 2010-05-09T20:50:00

C#

namespace ConsoleApplication1
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Please enter the letter A or B");
            string s = Console.ReadLine();
            A.Base baseClass = new A.Base();
            ;
            if (s == "A")
            {
                A.Foo f = new A.Foo();
                baseClass = f;
            }
            if (s == "B")
            {
                B.Bar b = new B.Bar();
                baseClass = b;
            }
            baseClass.Write();
            Console.ReadLine();
        }
    }
}
namespace A
{
    public class Base
    {
        public virtual void Write()
        {
            Console.WriteLine("I'm class {0}", this.GetType().ToString());
        }
    }
    public class Foo : A.Base
    {
    }
}
namespace B
{
    public class Bar : A.Base
    {
    }
}

Entering A prints out:

I'm class A.Foo

Entering B prints out:

I'm class B.Bar

Basic inheritance states that methods not need to be overridden as long as the base class has an implementation.

Pete O'Hanlon · Answer 3 · 2010-05-09T23:24:00

Solution 3

With the constraints you have in place, the only way to achieve this would be to use reflection. I wouldn't advise this as it adds a lot of runtime overhead.

Posted 9-May-10 23:24pm

Pete O'Hanlon

#realJSOP · Answer 4 · 2010-05-09T23:51:00

From what you've said so far, it looks like your best approach is just to write the code you need to write. I don't recall if you mentioned whether or not the 3rd party namespaces are the same (I don't see why they wouldn't be).

It sounds to me like your high-minded desires are holding the project up. If it were me, I would link to DLLs that aren't in the GAC so that they get shipped with the product, and at that point, you don't have to do anything weird in YOUR code because the DLLs it is compatible with are shipped with the product.

nagendrathecoder · Answer 5 · 2010-05-10T00:40:00

Solution 5

Thanks to all for help, i tried Reflection too but as Pete has mentioned, it is adding lots of overheads.
So, i have decided to overload my methods. :doh:
But it would be appreciable if someone comes with a concrete solution on this.

Posted 10-May-10 0:40am

nagendrathecoder

Problem regarding confilcting Class names

5 solutions

Solution 2

Solution 1

Solution 3

Solution 4

Solution 5

Add your solution here

Preview 0