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 s
Ravisankar, Madhusudhanan wrote:
In our project - which we build using nAnt 0.84 - if I change any
compiler option like "/clr", etc.,
You should upgrade to 0.85 RC3 or a more recent nightly as soon as
possible. Definitely do this before putting significant work into your
build files, becaus
Thanks, it works.
2005/8/16, Merrill Cornish <[EMAIL PROTECTED]>:
> Celio,
>
> You need to have matching xmlns declarations in both build files _or_ you
> need to qualify the include parameter.
>
> Merrill
>
--
Celio Cidral Junior
WEG Eletric
http://www.weg.com.br
Sorry Gert, you are right. I was not aware (until have debugged nant)
of the fact that VS.NET search for assemblies also in the directories
specified in the registry entry for both .net framework and visual
studio. That's why it found the assemblies even after I had removed
the HintPath.
Thanks!
Matt,
A simple version could parse tasks with literal pathnames and quietly
skip tasks that reference properties. Not perfect, but it would work
in many cases.
Merrill
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
I vaguely started looking at it a while ago but didn't get
much done. The current implementation uses an xslt stylesheet to process
the buildfile and generate the projecthelp output. Xslt probably isn't
really the right tool for this ( hey I was doing a lot of work with xslt
at the time and wh
