There was talk a little while back of making references framework aware. However the problem is if you specify a bare filename ( eg System.Data.dll ) how does the csc task know whether its a system dll to be resolved by currentframeworkpath or whether you expect to find it on the path. I guess if there is not frompath and no asis we can try it as a framework path and if it exists pass that to the compiler. Just thinking aloud - any ideas welcome.
Ian
I have two frameworks (net-1.0 and net-1.1) installed. I have a <csc> task that includes a reference to <csc> <includes name="System.Data.dll" frompath="true" />
When i compile with net-1.1 it passes the following (incorrect) option to the csc.exe compiler. "/reference:C:\WINNT\Microsoft.NET\Framework\v1.0.3705\System.Data.dll"
instead of: "/reference:C:\WINNT\Microsoft.NET\Framework\v1.1.4322\System.Data.dll"
When I do: <includes name="System.Data.dll" asis="true" />
it works, because csc finds the correct version of System.Data.dll by itself. Is it a bug?
Jarek
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
