How to resolve namespace name conflicts?

nuitari

There are three projects, A, B, and C. A is a desktop application, B and C are 2 class libraries
The citation relationship is as follows:
Project B references C and Project A references B and C. As a result, it was reported at compile time that the namespace names in C have duplicate names and conflicts. How to solve such problems?

几米的石头

attention,
Bangding!

kalian2000

Since C is referenced in B, it is not necessary to directly reference B in A.

haluvv

Are there two classes with the same fully qualified names in B and C? For example, there are such definitions in B.Dll and C.Dll:

namespace MyNamespace
{
  class MyClass {}
}

If so, appropriate modifications should be made.

nuitari

What I am talking about is actually a class dependency problem. C is a class library. Any project that needs the functions of this class library can be referenced, so projects A and B are referenced. B is a class library. Any project that needs the functions of this class library can be referenced, so A is referenced.
My current method is to modify the name, but then it is cumbersome to reuse.

Tokalian2000(SnowLover):
A quotes b for a function that requires b, and c for a function that requires c. This does not mean that b completely includes c in function, and makes another package.

Do you have any good suggestions? ? ?

vampire_66

You can use alias ~

kalian2000

Sorry, I may have misunderstood the meaning of the landlord ..

Can you paste the general call relationship and related code?

芬恩克莱尔

A quotes b for a function that requires b, and c for a function that requires c. This does not mean that b completely includes c in function, and makes another package.


Don't understand what you mean.

If B references C, it means that B has included all C functions. It's like if your .NET application needs to run, you need the complete .NET Framework, although the functionality it provides is not related to your application, or you can split C ... don't quote it twice ...

nuitari

Give a simple example:
C has a database class CDatabase (assuming this name), this class completes the basic operations of the database, such as: connect, disconnect, execute SQL statements.

B is another class library that encapsulates the processing of a particular aspect of the business, which requires reading and writing database data, so a class library C is introduced in the project, so that B can use the classes in C.

A is an application that is responsible for managing the entire information system, which of course includes managing the part contained in B, so B is introduced into the project, so that the classes in B can be used. However, at some point A needs to access the database directly, so it refers to C and wants to use the classes in C to access the database.

The so-called reference is to include a dll file into the project. Found in actual use, if you do this, you will have spatial naming conflicts
Please express your opinions.

堕之旋律

Bangding!
SF