Quantcast
Channel: Handling namespace collisions
Browsing latest articles
Browse All 5 View Live

Handling namespace collisions

Thanks Kount -- that is a reasonable workaround.  I didn't realize that the compiler searches up the namespace chain like you mentioned.  I tried this out and it fixes the problem.

View Article



Handling namespace collisions

I see, still though, the search for System would go up the namespace chain starting from Foo.Bar.Test, then Foo.Bar, then Foo, where it stops since it finds Foo.System. There is no way of changing this...

View Article

Handling namespace collisions

 Koundinya Veluri wrote:I'm assuming the namespace containing the class you are testing is Foo.System, and that the default namespace of your test project is Foo (this is one way to produce the...

View Article

Handling namespace collisions

Hi James, I'm assuming the namespace containing the class you are testing is Foo.System, and that the default namespace of your test project is Foo (this is one way to produce the scenario you...

View Article

Handling namespace collisions

I have a new test project that includes a reference to the global System.dll as well as another private System.dll that I'll call Foo.System.dll.  My problem is that the autogenerated code in...

View Article

Browsing latest articles
Browse All 5 View Live




Latest Images