Heya Merrill,
> If you parse tasks, then you would also (I think) have to parse
> properties
> since the include pathname could be defined by property expansion. However,
> properties can be conditionalized by tasks, so they have to be parsed,
> and
> properties get defaults by command lin
Matt,
>>> -projecthelp should parse any include tags
I think the problem is with the camel getting his nose in the tent. :-)
If you parse tasks, then you would also (I think) have to parse
properties since the include pathname could be defined by property expansion.
However, properties can b
Heya Ian,
> >Would anyone be interested in a patch for that behaviour? Or is it
> >undesirable (as it seemed to be for Gary at least)?
> >
> >
> Definately.
I take it that definitely was directed at the "interested in a patch". ;)
> I vaguely started looking at it a while ago but didn't get
>
Matt Trentini wrote:
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it
Title: NantScript change does not trigger C# compiler
Hi all,
In our project - which we build using nAnt 0.84 - if I change any compiler option like "/clr", etc.,
the C# / C++ project is not compiled in case of an ordinary build - i.e. - "no rebuild".
I dont know whether nAnt/ the c# /
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it seemed to be for Gary at
I'm attempting to use nant 0.85, rc3 with .NET 2003, but running into
problems when running the link stage of processing a solution file.
I've created a simple build file that uses the task to
build a solution file created by the IDE. internally, the solution
file references other project files.
Celio,
You need to have matching xmlns declarations in both build files _or_ you need
to qualify the include parameter.
Merrill
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA *
It sounds a little strange, but it seems the task does not
work properly when you set the xmlns attribute for the
element.
I have a build script with xmlns attribute set to something, and a
number of tasks.
http://nant.sf.net/schemas/nant.xsd";>
etc...
http://nant.sourcefor
Hi Gert!
I'm working with VS.NET 2003 and it seems to have a different
behaviour. I tried to compile with NAnt a project which has a
reference to a CrystalReports assembly and the build failed because
the hint path was set to a relative path which does not exist (I'm
using the build script file wi
Matt,
I don't believe you can do what you would like to do. As I remember from some
previous question, --projecthelp doesn't actually cause the NAnt file to be
processed so tasks and ${propertyname} substitutions aren't executed.
Instead, --projecthelp merely reads the NAnt file serially loo
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Célio Cidral Junior
> Sent: dinsdag 16 augustus 2005 14:38
> To: nant-users@lists.sourceforge.net
> Subject: [Nant-users] Does it search for assemblies in GAC?
>
> Hi,
>
> When building via tas
Hi,
When building via task, does NAnt search for assemblies in
the GAC when it does not find them with HintPath? I refer to those
assemblies referenced by the projects.
Thanks,
--
Celio Cidral Junior
WEG Eletric
http://www.weg.com.br
---
SF
You are right, the web project had not the same configuration of the
solution file. For some reason VS.NET was not creating that
configuration for the project.
Thanks,
Celio.
2005/8/12, Gert Driesen <[EMAIL PROTECTED]>:
> Celio,
>
> The project is probably skipped because the name of the projec
Matt Trentini wrote:
...Which works fine. :) What I'd like to do however is get project help
on one of the specific build files that included targets from both the
specific build file and the common build file. Ie, I'd like to be
able to do:
nant -buildfile:specific.build -projecthelp
An
15 matches
Mail list logo