Ok tested with the latest nightly builds, it works.
Thanks!!
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 4 November 2003 5:29 PM
To: Eddie Tse; [EMAIL PROTECTED]
Subject: Re: [nant-dev] solution task bug in nested build
What version of NAnt are you
Hi All,
I have a large multi-solution project and the solution task does not build
properly if it is called within a nested nant task because the full path
to the solution file is not used. Patch attached.
Cheers,
Eddie
Index: src/NAnt.VSNet/Solution.cs
resources etc when you want to do a quick test build.
Another option is maybe delete the whole output directory. Suggestions?
Eddie
-Original Message-
From: Erick Thompson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 9 September 2003 3:05 AM
To: Eddie Tse; [EMAIL PROTECTED]
Subject: RE
Hi All,
I've made a quick patch to add a clean action to the solution task.
Basically it will remove all the primary output files. I would like some
feedback on this.
solution solutionfile=WindowsApplication.sln configuration=debug
action=Clean
/solution
Cheers,
Eddie
? patch.txt
Index:
I noticed this today as well with the solution task and it is not the same
behaviour using VS.NET. For me, unreferenced assemblies do not get copied
by VS.NET to the output directory. It only copies assemblies that are
referenced directly in your project file or indirectly by a referenced
];
-Original Message-
From: Matthew Mastracci [mailto:[EMAIL PROTECTED]
Sent: Saturday, 23 August 2003 1:11 AM
To: Eddie Tse
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] solution task fixes
Eddie - ignoring non-csproj and non-vbproj files looks good. We
shouldn't do this without at least warning
Hi,
If you call another build file in a sub directory using the nant task and
the nested build file contains a solution task The path name used by the
nested solution task is not correct. This patch fixes that problem.
Cheers,
Eddie
Index: Solution.cs
Hi All,
I've been experimenting with the solution task from CVS and had made a few
changes in order to make it work for me.
Added the NoWarn option from VS.NET 2003
I have SQL projects as well as deployment projects in my solution, so
ignored those.
And the webmapcollection was using the path
