G
Guest
Hya, I am working on an application which is divided into many projects. All of the projects are are divided into two major portions...
- the persistance (all related projects in a same solution)
- the business (all related projects in a same solution)
If a project of persistance requires reference of another project located in persistance tier, I add reference using the PROJECTS tab.
Now the problem comes when I have to add a reference of project which is not a part of solution... I have to use the FILE reference. Now big big problems happens...
PROJECT_A uses PROJECT_B
I add reference of PROJECT_A in PROJECT_C
(as a result, it will copy both DLL's into the bin of PROJECT_C).
Now I also need to access PROJECT_B in PROJECT_C... I add file reference again...
Now problem occurs... for sure, if there is a version difference of PROJECT_B being used by PROJECT_A and PROJECT_C, the compiler gives warning that it cannot copy DLL blah blah... while building PROJECT_C.
Though I think I am unable to explain the problem properly, but still I expect an Excellent Answer! ... you know why?
eff-kay
- the persistance (all related projects in a same solution)
- the business (all related projects in a same solution)
If a project of persistance requires reference of another project located in persistance tier, I add reference using the PROJECTS tab.
Now the problem comes when I have to add a reference of project which is not a part of solution... I have to use the FILE reference. Now big big problems happens...
PROJECT_A uses PROJECT_B
I add reference of PROJECT_A in PROJECT_C
(as a result, it will copy both DLL's into the bin of PROJECT_C).
Now I also need to access PROJECT_B in PROJECT_C... I add file reference again...
Now problem occurs... for sure, if there is a version difference of PROJECT_B being used by PROJECT_A and PROJECT_C, the compiler gives warning that it cannot copy DLL blah blah... while building PROJECT_C.
Though I think I am unable to explain the problem properly, but still I expect an Excellent Answer! ... you know why?
eff-kay