Make sure you've set Script Source Access in your security settings
and set Write access to your bin directory. At some point I'll put in
a URL - path mapping in the solution task to get around having to use
WebDAV.
brant wrote:
The NAnt solution task uses WebDav to retreive the project file
Does NAnt shadow copy DLLs right now? I seem to remember seeing a
shadow copy cache directory (though that could be NUnit related)
[EMAIL PROTECTED] wrote:
What os are you running on ?
- We are running on Win2k workstation and server.
What happens if you copy it to the local disk -
I've discovered a few bugs so far. :)
* NUnit2 task is broken when specifying multiple assemblies with a
fileset
* FileSet's includeList element is broken
These are fixed in CVS. I'm going to respin the build while I can to
avoid any support messages for these items.
Matt.
scanning.
* Resgen file generation correctness fixes.
* Added support multiple delimiters and string trimming to LoopTask's
file line mode.
* More support for CSC/VBC command-line options.
Thanks!
Matthew Mastracci
---
This SF.net email
I added fileset support to the NUnit2 task earlier - but this shouldn't
affect the assemblyname attribute.
Scott Hernandez wrote:
That assemblyname attribute is really a nunit assemblyname(FilePath). It
really needs to be a full filepath to the file.
I have updated the NUnit2Test to resolve the
Make sure that you're using the same version of NUnit for linking your
test assemblies that NAnt uses. You'll get this error if there is a
mismatch. I'm not sure what we can do to fix the issue of linking
against the wrong NUnit, but I'm guessing that this is what the problem is.
Anthony
Before 0.8.2 goes into release mode, are there any outstanding issues
that anyone needs addressed? Specifically:
- Any showstopping bugs? There have made some significant changes to a
number of core classes. There's always a chance for a new bug or
regression to pop up. Is the SharpZipLib
Sweet! I can't wait to try out the logging. One thing I would like to
implement is having the LogPrefix stuff added by default - you would be
able to just specify Log.WriteLine and have the prefix/indent added by
default.
Once this stuff has baked in CVS for a while, perhaps we should
Sure- here's the current source.
The project is at the point where it can compile every VS.NET project
I've thrown at it. Brant helped me add VB.NET support to the task as
well (I haven't tested this). I've even got a very basic web project
compiler, but this is not even close to complete.
(other than coding, code reviews,
testing, and releases :) along these lines?
--
Matthew Mastracci [EMAIL PROTECTED]
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
--
Matthew Mastracci [EMAIL PROTECTED]
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun
This patch adds support for running NUnit2 tests with a fileset source
for assemblies. This allows you to specify:
nunit2
test
includesList name=tests.txt /
/test
/nunit2
to run all of the tests in test.txt. It still supports the old syntax.
Any objections?
Matt.
? patch.txt
?
This patch re-enables the behaviour I checked in earlier, but properly
supports exclude paths. I wrote a number of exclude path tests in
DirectoryScannerTest.cs to exercise a number of pieces of exclude
behaviour, as well as running a test-build with this patch. Everything
works well.
The
Whoops - I just noticed that everything did end up getting applied.
Thanks...
I'm not sure, but the MoveTask looks like it may been to be fixed up as
well. I think a unit test needs to be written to see if the
functionality is correct (the current one succeeds, but I think it only
tests a
This patch does a test to see if a pattern should result in a recursive
search. Recursive searches are triggered by either wildcard directory
names or the ** path separator (see the comments for more detail).
The speed increase should be visible for some cases, but you should see
improvements
Whoops- I keep forgetting the -u :) I can check this stuff in on my end.
Ian MacLean wrote:
Matthew,
I applied your patches to Fileset.cs and directoryscanner.cs as well
as the new copytest.cs. The part of the patch fixing copy and delete
failed to apply against my tree - maybe because the
?
Thanks,
Gert
--
Matthew Mastracci [EMAIL PROTECTED]
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can
The following patch fixes directories getting treated as files in a
FileSet. This behaviour was breaking certain copy operations. It also
fixes the Delete and Copy tasks to handle the new behaviour, allows
delete and copy tasks to handle read-only files, adds a CopyTest unit
test, and
I'm taking a look at this one. The problem is that FileSet is adding
matching directories. Right now, I'm writing unit tests and fixing both
the delete and copy task to work sanely.
Gert Driesen wrote:
Hi,
Apparently there's a bug in the CopyTask when directories included
using a fileset
)
+dstInfo.Attributes = FileAttributes.Normal;
}
} else {
string msg =
String.Format(CultureInfo.InvariantCulture, Could not find file {0} to
copy., srcInfo.FullName);
Philip Nelson wrote:
--- Matthew Mastracci
I think it's a great idea to have a NAnt GUI tool. I'm in the process
of converting over our shop from batch files to NAnt for our nightly
builds and I'm looking forward to having a GUI to run my builds
(especially unit tests) before checking in. Unfortunately it'll be a
little while before
delim=,
property name=x /
property name=y /
/foreach
--
Matthew Mastracci [EMAIL PROTECTED]
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Should we change the following lines in the LoopTask? Currently, the
string is split based on a single delimiter. Since String.Split()
supports a character array, we can remove the char array [0] indexer and
have it split on any character in the delim property. I can fix this
and check it
pattern=$[^#].* /
Any comments?
Matthew Mastracci wrote:
Should we change the following lines in the LoopTask? Currently, the
string is split based on a single delimiter. Since String.Split()
supports a character array, we can remove the char array [0] indexer
and have it split on any
in
the absence of the web server?
Brian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Matthew Mastracci
Sent: Saturday, February 22, 2003 8:02 AM
Cc: [EMAIL PROTECTED]
Subject: [nant-dev] Visual Studio solution builder
Now that NAnt 0.8.01 has been released
Regardless of future implementation tasks, would anyone object if I
enhance the ExternalProgramBase to indent output from called programs? :)
I agree that we need a more powerful logging system, but as things stand
right now, we have a half-decent one that gets the job done. Once 0.8
is
I just checked in a fix for the LicenseTask to convert the target to
uppercase. Apparently, some licensing systems expect this, while others
are case-insensitive. The new behaviour matches that of Visual
Studio.NET, however.
Matt.
---
That would be me - I have a VSProj task that handled .csproj files, but
I haven't had a chance to clean it up for NAnt yet.
Javier Ochoa Lopez wrote:
New to nant, please help...
I am trying to have automated builds for my project.
I have seen at the forum some ideas about having a csproj task
The code and unit tests look good for style and completeness. I'm in
the process of getting VJ# set up so I can't run the test just yet.
For a task related to VJ# (or something else not part of the default
.NET install), should this be a loadable task? Someone without the VJ#
install would
*gulp*. resx and license were recently added by me. You're right
that the paths should be relative to the project, and I believe the
solution you have is correct.
If you have a patch, send it my way and I can check it in, or I can take
a look myself. The unit tests *may* need to be modified
While everyone's awake in here - can I ask which branch tag the next
version of NAnt is coming from? I'm sitting on the resx and license
tasks for the moment. As well, I'm still trying to get CVS under
windows to work over PLink to sourceforge so I can actually check in. :)
Kevin Miller
for now the functionality to produce the NMake makefiles?
In any case I would like to keep SLingshoT as a command line util along with
a NAnt task.
Szymon.
-Original Message-
From: Matthew Mastracci
To: Ian MacLean
Cc: Szymon Kobalczyk; '[EMAIL PROTECTED]'; 'Bernard
Vander Beken'
Sent: 2002
types. Projects in C++
and C# are supported, including Web Projects.
If your compiler/task does the same as SLiNgshot, you may want to help
enhancing it.
Best regards,
Bernard
[1] http://nantcontrib.sourceforge.net/
-Original Message-
From: Matthew Mastracci [mailto:matt;aclaro.com
I have a task for NAnt that will compile projects exactly as VS.NET
does. Please see my earlier messages for more information, and let me
know if you are interested in trying out the custom NAnt task.
Szymon Kobalczyk wrote:
Ok, here is the last problem I had to face today. Some of our
I've got the VSProj task building and working (but not fully integrated
yet). I noticed that SLiNgshoT does something similar to this, but I
think that this project has a greater understanding of VS.NET project
files. I've managed to correctly reproduce the (ugly) handling of .resx
-
101 - 135 of 135 matches
Mail list logo
