[nant-dev] SolutionTask / VCProj support / Additional include directories

2004-07-06 Thread tbarrere
Hi, here's a small patch proposal for VCProject.cs. When using the solution task with .vcproj (c++) projects, additional include directories are concatenated to a single /I folder1;folder2 parameter in the call to cl (splitting is only based on comma). This doesn't work, as the compiler

Re: [nant-dev] SolutionTask / VCProj support / Additional include directories

2004-07-06 Thread Gert Driesen
Thibaut, This change has been committed to cvs. Thanks, Gert - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 06, 2004 1:19 PM Subject: [nant-dev] SolutionTask / VCProj support / Additional include directories Hi, here's a small patch proposal

[nant-dev] SolutionTask

2004-01-16 Thread Martin Aliger
Hi all, I found one very annoying feature/bug of solution task: Projects (.csproj) are loaded into hashtable regarding their guid. But if two projects with same guid are loaded, no error/warning is issued and one of those projects disappears! Such projects could be created by copying and

Re: [nant-dev] SolutionTask

2004-01-16 Thread Nicklas Norling
It is not possible to have two identical GUIDs, such a case is an indication of corruption in the csproj file and should not be allowed. VS tries to sort things out (give it a second try if you will) by trying to look at project names and se if that would give a valid and unique combination, that

Re: [nant-dev] SolutionTask

2004-01-16 Thread Ian MacLean
I'm convinced. Committed. Ian I think Martins patch should go in and I love the error message, very describing giving both the problem and solution. /Nicke Is this the right patch ? if it is possible to have two valid projects with an identical guid should we use a different key for the hash

[nant-dev] solutiontask outputdir attribute

2003-08-27 Thread Martin Aliger
Hi, new outputdir attribute works great for assembly output but for documentation makes few more folders under outputdir when doc output is set e.g. to 'debug\bin\aa.xml'. This should patch it: --- E:\src\nant\distrib\NAnt.VSNet\ConfigurationSettings.cs Tue Aug 26 22:04:44 2003 +++