I apologize in advance if I'm posting a question that has recently been answered. Many posts as oflate have gone many miles over my head...
Developersin my shoprecently got sick of reference problems and began using project references (while I was in a meeting Friday afternoon). This is good from
Hi all,
What should this code in Reference::GetReferenceFiles
do?
// Get a list of
the references in the output directory
foreach (string referenceFile in
Directory.GetFiles(fi.DirectoryName, "*.dll")) {
// Now for each reference, get the related
files (.xml, .pdf, etc...)
string
That's correct behavior that also happens when compiling from VS.NET; referenced DLLs
get copied to the executable folder. You can change this behavior from VS.NET if you
go to the properties of the reference and set copy local to false. Unless you are
putting probing directives into your
assembly which it can find via the reference path.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom
Cabanski
Sent: Tuesday, 2 September 2003 10:21 PM
To: Martin Aliger; [EMAIL PROTECTED]
Subject: RE: [nant-dev] solution task question
That's correct behavior
- Original Message -
From: Eddie Tse [EMAIL PROTECTED]
To: 'Tom Cabanski' [EMAIL PROTECTED]; 'Martin Aliger'
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 2:28 PM
Subject: RE: [nant-dev] solution task question
I noticed this today as well with the solution task
]
Subject: RE: [nant-dev] solution task question
That's correct behavior that also happens when compiling from VS.NET;
referenced DLLs get copied to the executable folder. You can change this
behavior from VS.NET if you go to the properties of the reference and set
copy local to false. Unless you
