Hi all,
I was quite long away, but now again working with NANT. I need some changes, so there
is what I suggest. I will try get smaller blocks to be easy.
First RESGEN. It writes some annoying messages even when verbose=false. It goes to
ExternalProgramBase.cs:
---
Hi,
when working with NUnit2Task I saw that the output of the test always showed up twice
when specifying a formatter.
This is caused by always adding a defaultFormatter, even when there are formatters
specified.
Added: if (_formatterElements.Count == 0)
The patch is copied below, also
Last one - and I'm not sure there.
There are problems with references between projects when projects have different
output paths. Project references are ok, but external refenreces sometimes brokes.
Currently nant compares files as full pathnames using path from HintPath attribute. I
suggest
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
I am not able to figure out what is the problem in below fragment.. it use
to work before
echo message=${OutputFolder}/
foreach item=File property=filename
in
items in=${OutputFolder}
includes name=**/m*.dll/
includes name=**/m*.exe/
/items
/in
do
regex
Hi Yogesh,
items is a fileset, so the attribute should be basedir instead of in.
this works for me:
?xml version=1.0?
project name=test description=test default=test
property name=OutputFolder value=C:/Dir//
target name=test
foreach item=File property=filename
in
items
Eddie - ignoring non-csproj and non-vbproj files looks good. We
shouldn't do this without at least warning the user that we are ignoring
their projects, however. Can you add a log message to this test?
Eddie Tse wrote:
Hi All,
I've been experimenting with the solution task from CVS and had
I'd recommend against comparing only filenames. This will likely end up
causing trouble down the line. VS.NET is certainly a mess when it comes
to hint paths, but I've found that they are generally accurate. I don't
even think it uses them half of the time. :)
Can you describe your
No, it's not. It's an attribute of a build element/type, not a task. For
now, only tasks (and their attributes) are documented.
Gert
- Original Message -
From: Yogesh Shetty [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 1:23 PM
Subject:
Solution task sometimes puts two dots in resource names where there should only be
one. This patch fixes the problem.
Can someone apply it for me?
The patch is inline below my signature.
Thanks
-
Tom Cabanski, President
Objective Advantage, Inc.
Hi Jasper,
I'm not sure if this is the correct fix for this issue ...
I'd rather remove the default formatter altogether, but that would break
backward compatibility. But if we can correct wrong behaviour, we should do
it as soon as possible ...
Ian, what do you think ?
Gert
- Original
Hi,
I suggest to override OutputPath in .csproj in build-file. It could be useful to write
some easy to maintain build files as that:
target name=build
solution configuration=Release output=${build.dir}
projects
includes
Maybe this is why (clipped comment from a distantly related thread
below) I didn't see this if it's already documented, but it took me a
bit of serendipity (just happening to remember wondering why in
tarnation the force attribute for call/ was there to begin with from
sleep-deprived reading many
Just started trying to use Nant yesterday, so forgive me if this is a
known issue.
I created a solution for the HelloWorld example with one C# project in
it (HelloWorld-cs.csproj). Using the following build script, Nant
0.8.3-rc2 compiled it just file:
---
?xml
14 matches
Mail list logo
