References

[Demetri]

I have a solution with class library projects. One class library we'll call
Project B is dependant on another class library project we'll call Project A.

I also have a setup project that installs those librarys in c:\ program
files\mydlls. It also installs them in the GAC.

Now, my problem is that if I have a new solution that wants to use Project B
it also has to reference Project A to do so. I wish that all they would have
to do is reference Project B and be done.

Is it possible?

--
-Demetri

[Peter Bromberg [C# MVP]]

RE: References

If an assembly has a dependency on another assembly, that's the way it is.
If you have control over the code, consider refactoring out the portion of
code that is needed and put it into both assemblies.
Another possible alternative is to use ILMerge to merge both into a third
assembly, but this all really sounds more like an architectural defect if it
is that important.
Peter

--
Co-founder, Eggheadcafe.com developer portal:

http://www.eggheadcafe.com

UnBlog:

http://petesbloggerama.blogspot.com

"Demetri" wrote:
[color=blue]
> I have a solution with class library projects. One class library we'll call
> Project B is dependant on another class library project we'll call Project A.
>
> I also have a setup project that installs those librarys in c:\ program
> files\mydlls. It also installs them in the GAC.
>
> Now, my problem is that if I have a new solution that wants to use Project B
> it also has to reference Project A to do so. I wish that all they would have
> to do is reference Project B and be done.
>
> Is it possible?
>
> --
> -Demetri[/color]