RE: [Nant-users] Framework Targeting

2003-07-21 Thread Anthony LoveFrancisco
EMAIL PROTECTED] | Sent: Monday, July 21, 2003 11:14 AM | To: Miller, Kevin; [EMAIL PROTECTED] | Subject: Re: [Nant-users] Framework Targeting | | | Try | | asis="true" | | instead of frompath="true". | | This is based on the fact that csc.exe from a particular CLR | is a

Re: [Nant-users] Framework Targeting

2003-07-21 Thread Ian MacLean
not work unless the framework tools are in the path. So I still need vcvars32.bat settings present. -Original Message- From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2003 11:14 AM To: Miller, Kevin; [EMAIL PROTECTED] Subject: Re: [Nant-users] Framework Targeting

RE: [Nant-users] Framework Targeting

2003-07-21 Thread Miller, Kevin
AM To: Miller, Kevin; [EMAIL PROTECTED] Subject: Re: [Nant-users] Framework Targeting Try asis="true" instead of frompath="true". This is based on the fact that csc.exe from a particular CLR is able to locate the correct system libraries, when you don't specify the pat

Re: [Nant-users] Framework Targeting

2003-07-21 Thread Jaroslaw Kowalski
your PATH variable, you should avoid using "frompath" at all. Jarek - Original Message - From: "Miller, Kevin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 21, 2003 5:35 PM Subject: [Nant-users] Framework Targeting We are targeting the 1.1 fr

RE: [Nant-users] Framework Targeting

2003-07-21 Thread Erv Walter
exe will find the correct reference (and Nant will use the correct csc.exe because you set the curentframework). -Original Message- From: Miller, Kevin [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: [Nant-users] Framework Targeting We are targ

[Nant-users] Framework Targeting

2003-07-21 Thread Miller, Kevin
We are targeting the 1.1 framework. We changed our build scripts to include: However I noticed that 1.0 dlls were still being referenced for assemblies referenced via frompath="true". The cause was the fact that I had the builds running from a ".NET command prompt" or a command environment with