Today I am faced with a curious challenge...
This challenge involves two .NET libraries that I need to reference from my application. Both of which I have no control
You need to use an extern alias - introduced in C# 2.
Anson Horton has a walkthrough on his blog which you may find useful.
I think you have to use extern alias
See http://msdn.microsoft.com/en-us/library/ms173212.aspx
Here's a walkthrough. http://blogs.msdn.com/b/ansonh/archive/2006/09/27/774692.aspx
I'd be surprised if you can do this, without using reflection.
It might be easier to create your own FooWrapper and BarWrapper dlls which reference foo and bar and expose their contents again under different namespaces.
You could use the "Aliases" property for resolving conflicts. Select the library and open Property window. This is already discussed in this SO post
Wow, thats tricky. I tink, I would create two wrapper-DLLs:
and support different namespaces there.