Adding references: the details
- From: _DS <_DS@xxxxxxxxxxxxxxx>
- Date: Tue, 17 Jan 2006 04:17:16 -0500
The two obvious methods for ref'ing assemblies are:
Add a reference and 'Browse' for the actual DLL
OR
Add existing project to the solution, then add a ref to 'Project'.
1: I'd like to find out what the latter method is doing.
I'm assuming that it makes sure that debug exe gets matched to
debug DLL, etc. What else is going on? (I couldn't locate much
info in MSDN)
2: This method induces a couple glitches: If assembly A refs
assembly B, then the project for assembly A works as expected:
Just add assembly B to A's solution, then set a reference to B.
Now what about the final exe that uses assembly A: Add A to
the exe's solution, then set a reference to A. You'd expect that
B would be automatically ref'd by A's project. No such luck. The
build generates an error as if A can no longer find assebly B.
I hope that was understandable. Any way to simplify that, or must
the top solution go through the add-to-project and add-ref-to-project
for every sub-sub-sub-assembly that's referenced?
.
- Follow-Ups:
- Re: Adding references: the details
- From: Frans Bouma [C# MVP]
- Re: Adding references: the details
- Prev by Date: Re: Document.Open Office Example
- Next by Date: Re: Difference between vs2005 WebBrowser and AxWebBrowser components?
- Previous by thread: RE: Asynchronous events exception handling
- Next by thread: Re: Adding references: the details
- Index(es):
Relevant Pages
|
