Hi
I've just published the details of automating Sandcastle CTP
(http://blogs.msdn.com/sandcastle) using NAnt.
I managed to generate the documentation for my NLog project using
Sandcastle instead of NDoc. There are some issues, but the doc is
already usable. The script is non-trivial, and uses
Gary Feldman wrote:
> Jaroslaw Kowalski wrote:
>
>> Gary Feldman wrote:
>>
>>
>>> ...
>>> This would remove one of the major advantages that NAnt has over VS2003,
>>> namely it can build the
>>> solution much more rapidly tha
Gary Feldman wrote:
> Jaroslaw Kowalski wrote:
>
>> I never used the task. My personal opinion is that solution
>> building should be placed in a separate utility and NAnt should only
>> spawn it instead of implementing the entire build logic in-process.
>>
Bonio Lopez wrote:
> Hi Jaroslaw,
> Why do you create a nant tasks "manually" instead of using solution task ?
> Is it because VS2005 not supported so far?
> Is somebody working to support VS2005 solution task?
> With best regards,
> Boni
>
I prefer "clean" tasks, because I prefer to specify so
Hi!
I often face the problem of synchronizing Visual Studio (both 2003 and
2005 versions) projects with NAnt. I usually build with NAnt but want to
provide Visual Studio build files for my users. The problem is that I
tend to forget to update all the projects (*.csproj) with the newly
files or
Hi!
I've just had a 10-minutes VB.NET course and the result is included:
You need to:
1. Add NLog.dll reference to your project.
2. Add App.config file to your project as it tells NLog the logging rules.
If you don't do it, NLog will output nothing. Alternatively use other
configuration metho
Yes. Anything with "else" semantics is needed badly.
Jarek
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: "Nick Zigomanis" <[EMAIL PROTECTED]>;
<[EMAIL PROTE
It should be possible to use the if() operator:
The semantics of if(a,b,c) is: "if a=True then b else c" which is
exactly what "a ? b : c" operator from C/C++/C#.
Gert, what do you think of extending it to (backward compatible):
if (condition1,result1,condition2,result2, ..., conditionN,resul
string::concat() isn't supported. Use + operator for
concatenation. Where did you find this function?
Jarek
- Original Message -
From:
McCullough, Gary
To: [EMAIL PROTECTED]
Sent: Monday, September 13, 2004 3:21
PM
Subject: [Nant-users]
string::concat?
Use test="${directory::exists(build.dir)}". Properties inside expressions
can be accessed directly without any decoration.
Jarek
- Original Message -
From: "Burton, Kevin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 11, 2004 12:27 AM
Subject: [Nant-users] Testing
Hi!
Inspired by the Gump project, I started
looking at various open source projects (log4net, NDoc, NAnt, NUnit,
ICSharpCode.*) to see how they are built and how they interoperate.
The typical problem is: you want to build a
component (one or more DLLs + some EXEs) based on a set of other
Hi!
I'd like to let you know about the new open source project called "NLog"
which is a simple but quite powerful logging library for .NET.
The design goals:
- ease of use (uses familiar WriteLine() style interface)
- maintainability (trivial to configure and re-configure)
- speed (uses "zero al
> This is ofcourse the best solution for the issue Jeroen brought up, but
that
> other users might still expect the possibility to use relational
operations
> on versions. Meaning: should the following functions return a version
data
> type :
>
> assembly::get-version(string)
> file::get-f
Gert, how about adding a nant-level functionality for that?
...
About the script task: Make sure you don't have xmlns defined in your
element (to support intellisense). Mono seems to have problems
with that.
Jarek
- Original Message -
From: "Jeroen Zwartepoorte" <[EMAIL PROTECTED]>
You can get pretty good intellisense with VS.NET using task.
VS.NET is able to suggest elements, attribute names and values in this case.
Expressions and functions aren't suggested nor verified but that's beyond
the scope of what XSD schema can provide.
Simple HOWTO:
1. You run this build file w
Ian, Gert, how about this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg03737.html
Some time ago I posted an implementation of "fileset" family of functions
that works with named filesets. Can we include it in NAnt?
Jarek
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
+1 to either of the ideas. Having an else is a must.
I wonder if it would be doable to have:
'then' tasks here
'else' tasks here
Jarek
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "McCullough, Gary" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thur
You can use the task or if attribute on targets and tasks.
For example
a)
b)
c)
Alternatively there's unless attribute which can be used instead of if.
Jarek
- Original Message -
From: "Burton, Kevin" <[EMAIL PROTECTED]>
To: "McCullough, Gary" <[EMAIL PROTECTED]>;
<[E
if="${directory::exists(src.dir + '/ac')}"
or even better:
if="${directory::exists(path::combine(src.dir, 'ac'))}"
Property names are unquoted within expressions.
Jarek
- Original Message -
From: "Felice Vittoria" <[EMAIL PROTECTED]>
To: "Nant-Users (E-mail)" <[EMAIL PROTECTED]>
Sent:
On Wed, 21 Jul 2004, Troy Laurin wrote:
> Jarek, others,
>
> I kind of like the idea of a property having a type, but I have a few
> questions regarding implementation...
>
> In the following...
>
>
>
>
> If the default type for properties if none is specified is 'string',
> then what is the typ
Hi guys!
I'd like to propose the introduction of typed
properties to NAnt. Currently properties are stored as strings which has many
drawbacks, esp. when used within expressions.
For example:
...
this test fails because:
1. "a" is stored as a string
2. equality operator promotes
Are you sure that you have .NET 1.1 SDK too (the one that comes in setup.exe
and includes documentation)?
If you do, then there must be something wrong with your registry.
Jarek
- Original Message -
From: "Malcolm MacLucas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Gert Driesen" <
Hi Anthony!
Are you going to add support for nant::functions to NAntpad? Having an
intellisense-like interface would be cool.
Jarek
- Original Message -
From: "Anthony Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 6:46 PM
Subject: [Nant-users] Nantpad 0
How about this?
Jarek- Original Message -
From: "Nick Zigomanis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 03, 2004 9:08 AM
Subject: [Nant-users] uptodate files is deprecated
Hi all,
The uptodate test warns that it
NAnt detects the OS and the version of .NET it's running on and
automatically sets the "nant.settings.currentframework" property based on
this. For example when running on .NET 1.0 it will set "net-1.0" framework,
on mono it will be "mono-1.0".
If you have two frameworks installed .NET 1.1 will be
There's no support for this in 0.8.4. To use expressions you need to use the
nightly build of NAnt available at:
http://nant.sourceforge.net/builds/
These releases are actually pretty stable and I use them on a daily basis.
You can now write:
... tasks here ...
More information availabl
Hi Ian!
Please, don't do this kind of tricks. It is like shooting yourself in the
foot. Functions (by definition) should be side-effect-free and nobody is
advised to do otherwise.
I was just going to propose a patch that would prevent ANY writes to
property dictionary during property evaluation,
Can you re-run your build script with the latest nant nightly build? Make
sure to turn on verbose debugging and post the build log. I think Gert will
be interested in the results.
Jarek
- Original Message -
From: "Noah Davidson" <[EMAIL PROTECTED]>
To: "NAnt Users Mailing List" <[EMAIL PR
Finalization of domain
> TypeGatheringDomain timed out.
>
> BUILD FAILED
>
> /home/pmimmack/projects/nant/NAnt.build(74,9):
> AssemblyInfo file
> '/home/pmimmack/projects/nant/src/CommonAssemblyInfo.cs' could not be
> generated.
> Finalization of domain Ty
Can you try it with the latest nightly build? Many bugs were fixed since the
0.84 release including some that you mention.
Some test don't pass, anyway, but you should be able to use nant with mono
for some common tasks.
Jarek
- Original Message -
From: "peteMimmack" <[EMAIL PROTECTED]>
No it doesn't. NAnt only uses the compilers that come with .NET Framework
(csc.exe, vbc.exe, and so on). It emulates the behaviour of VS.NET when
compiling projects through task.
Looks like another compiler needs to be added ;-)
Jarek
- Original Message -
From: "Jean-Francois Gagnon" <
Try this:
http://nant.sourceforge.net/nightly/help/fundamentals/expressions.html
http://nant.sourceforge.net/nightly/help/fundamentals/functions.html
Jarek
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 10:20 PM
Subject: RE: Re: Re: [
How about this:
Jarek
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 9:58 PM
Subject: RE: Re: [Nant-users] Conditional copy
> Ian,
>
> Thanks for your response but i'm not quite there yet.
>
> I see lots of nant tasks that suppor
Getting nant to work with mono 0.31 is non-trivial. Can you update mono from
CVS and do:
$ export MONO_NO_UNLOAD=1
before running nant?
This is a workaround to a known bug in mono which messes up nant/nunit.
Jarek
- Original Message -
From: "Pedro Santos" <[EMAIL PROTECTED]>
To: <[EMAI
?
- Original Message -
From: "Pedro Santos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 08, 2004 11:33 PM
Subject: [Nant-users] NUnit
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutori
n fix many bugs.
Download and unzip this one:
http://nant.sourceforge.net/builds/nant-0.85-20040405.zip
and it should work just fine.
Jarek
- Original Message -
From: "Martin Gainty" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; <[E
Answer I got from Gert:
> Hi Gert!
>
> Do we have any date set for the 0.85 release?
No, not yet. I'll think about it, and see if I can create a to-do list
for the 0.85 release.
Gert - what do you think about releasing nant 0.85 around 1st of May? I
think we can get the expression evaluator issu
I presume you're using some pre-dinosaur Nant version. Can you download the
latest stable build and try again?
In general you should invoke nant in a directory where "nant.build" is
located not in the subdirectories.
Jarek
- Original Message -
From: "Martin Gainty" <[EMAIL PROTECTED]>
T
> Is this a "feature" of the so-called MS .Net XCopy deploy functionality?
Is
> there anything that I can do to ensure that the delete and copy will
> actually work, as this error is not really making life easy for a
hands-off
> build and deploy
It can be some anti-virus software doing their job.
You should reference bin\Debug\lib.dll instead of lib.dll
Hope it helps.
Jarek
- Original Message -
From: "Brian Beaudet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 06, 2004 10:54 PM
Subject: [Nant-users] Newbie Question Regarding Referencing Assemblies
> I've go
Yes, it's included in the nightly builds (since December 2003) and will be
included in future stable releases. It has been greatly enhanced since the
nant-ee-test1.zip release. See http://nant.sf.net/ for more information.
Documentation can be found at:
http://nant.sourceforge.net/nightly/help/fu
When invoked without parameters it prints out: "aaa zzz"
When invoked as "nant -D:property=value" it prints out "aaa value". The
command line arguments override global property definitions.
Hope it helps,
Jarek
- Original Message -
From: "Bonnett, Evan A" <[EMAIL PROTECTED]
Try this:
export MONO_NO_UNLOAD=1
before running nant. Make sure you're running from mono/cvs as this
"feature" was introduced recently and is not present in 0.31.
Jarek
- Original Message -
From: "Raúl Romero" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 31, 2004
Brian,
The answer to your question is "it depends":
As NAnt is evolving pretty fast, it might be reasonable to put the NAnt
binaries in your project directory structure. Some OSS projects
(SharpDevelop, I think) do it. This ensures build consistency.
I usually have the following project structur
There's a typo in your buildfile. You should use
instead of
I believe that NAnt should be detecting this and notifying user about it.
Somehow it doesn't. Gert?
Jarek
- Original Message -
From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
To: "José
Can you re-run your buildfile with -verbose -l:logfile options and send the
output?
Jarek
- Original Message -
From: "José Luis Barrera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 22, 2004 3:40 PM
Subject: [Nant-users] Problem with references...
> Hi all!
>
> I have
This is a general rule: all file paths are (or at least should be) relative
to the project that contains them. With this approach it doesn't matter
where you run your buildfile - it should always behave the same. NAnt tasks
take care of making all file paths absolute when passing them to external
u
It is possible through task. You simply have all your properties
in a separate buildfile:
properties.build
And you use it like this:
main.build:
Hope it helps.
Jarek
- Original Message -
From: <[
My vote is 2 (but make sure that "extraoptions" is needed in <5% cases).
Jarek
- Original Message -
From: "Clayton Harbour" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Kevin Dickover"
<[EMAIL PROTECT
There's a trick that uses task. Taken from my build script:
... do something with the properties ...
This will read ALL lines from "version.txt" (there's only one and that's the
trick) and set sooda.* properties appropriately.
See task documentation for more info. Hope it helps.
> I like the nested command and it looks like it would be easy to extend
> something like this into some sort of pluggable version control task.
Why do you want to do it? The last thing we need here is abstraction.
CVS is simple. Ultra simple. Various VCSes have different concepts and
features so
>
>
>
>
>
>
> There doesn't really seem to be an elegant way to do this...
What's wrong with the following syntax (modulo attribute names)? Why do you
require the separation of global vs command options?
Why would you want to enclose multiple cvs operations inside a single
task? Typically
lar to svn, once we have the tasks which
are command-line free we could provide exactly the same interface for
tasks.
What do you think?
Jarek
- Original Message -
From: "Clayton Harbour" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>;
Why do you want to split options into "global" and "command" ? This
introduces a new class of problem: "which option is global and which is
command".
Users don't like it. Really.
Jarek
- Original Message -
From: "Clayton Harbour" <[E
in a single attribute):
What do you think?
Jarek
- Original Message -
From: "Clayton Harbour" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Narendra Kulkarni"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
S
Clayton,
Wouldn't it be better to implement some meaningful attributes for this?
(BTW. I believe -Pd are so common that they should be on by default and
there should be an option to turn them off for special ocasions)
Jarek
- Original Message -
From: "Clayton Harbour" <[EMAIL PROTECT
If you use the nightly build (recommended):
If you want to use the release build, you task is the solution.
Jarek
- Original Message -
From: "Bonnett, Evan A" <[EMAIL PROTECTED]>
To: "'Gert Driesen'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, March 12, 2004 7:43 PM
Subje
Perhaps we could have a task instead that would be similar to
but accept WebDAV sources/targets.
+1 for the idea of removing WebDAV from the task.
Jarek
- Original Message -
From: "Erick Thompson" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>; "NAnt Users Mailing List"
<[
I add
support for overloading to NAnt?
Ian, Scott - what do you think?
Jarek
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Steven Hawkes" <[EMAIL PROTECTED]>; <[EMAIL PRO
Try
nant.settings.currentframework.sdkdirectory instead.
More specific: use
Jarek
- Original Message -
From: "Steven Hawkes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 06, 2004 8:03 PM
Subject: [Nant-users] Path to SoapSuds
Hi,
I am trying to find
Hi guys!
I've posted a patch for
http://bugzilla.ximian.com/show_bug.cgi?id=54980
The patch is here:
http://bugzilla.ximian.com/showattachment.cgi?attach_id=6839
This is not a perfect solution (it just boosts the timeouts), but helps in
running NAnt/NUnit on mono.
With this patch in place I w
Can you please download the latest nightly build? It should detect the
current framework properly.
If you prefer to stick with the release version (0.84), use "-k" parameter
on the command line or modify nant.exe.config to specify a default
framework. If you need more assistance, let us know.
Ja
>
>
> BUILD FAILED
>
> Tests Failed
>
> Total time: 4.8 seconds.
>
>
> BUILD FAILED
>
> Nested build failed. Refer to build log for exact reason.
>
> Total time: 5.4 seconds.
> Evan A. Bonnett
> Reynolds
I've committed a fix to this issue. Unfortunately NAnt is still not very
functional on linux/mono because of some strange issues with appdomain
finalizers.
Jarek
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Rodrigo B. de Oliveira" <[EMAIL PROTECTED]>;
<[EMAIL PROTEC
This looks like a syntax problem. NAnt is not very strict at
detecting syntax problems and sometimes it silently ignores them.
Can you post a failing portion of your buildfile to the
list?
Jarek
- Original Message -
From:
Adam Patacchiola
To: [EMAIL PROTECTED]
Sen
You use task.
NAnt decides whether to use any particular c# compiler depending on the
current framework.
You can set the framework in several ways:
1. Modify the "default" attribute in NAnt.exe.config. See this file for a
list of available frameworks.
2. Use -k parameter when invoking NAnt
na
This is a known issue. Download the latest nightly build and your issue
should be fixed.
BTW. You have a fully functional NAnt - the failing testcases are some minor
issues.
Jarek
- Original Message -
From: "Phil Winstanley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, Fe
This works for me:
*.resx resources are handled without problems here. Please check your paths
and/
Are you sure you're using a new version of NAnt to rebuild itself?
To rebuild NAnt you should use the mini-nant that comes in the package.
In general, when you're in nant base directory, run "bin\NAnt.exe" and nant
will rebuild itself into "build\".
Be sure that you have the appropriate .NET SDK
First, your DLL has to be named "somenameTasks.dll"
To use it, you have to either:
1. place the *.dll containing the task in nant/bin directory
2. place the *.dll somewhere else and add the path to
nant.exe.config:/configuration/nant/@taskpath
by default, it's set to ".\optional" which means th
> http://localhost/TI.mysol.mysolPortal/TI.mysol.mysolPortal.vbproj";
>
>
path="D:\Projects\TI\TI.mysol\TI.mysol.mysolPortal\TI.mysol.mysolPortal.vbpr
oj" />
>
>
>
>
>
> And got the same response.
>
> Any ideas on what this means?
Slingshot is a bit outdated. Use task from the nant core.
Jarek
- Original Message -
From: "Bryan Andrews" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 06, 2004 2:32 PM
Subject: [Nant-users] Slingshot
Hi,
I have installed nantcontrib and slingshot *seems* to be
Have you installed .NET Framework SDK ?
Jarek
- Original Message -
From: "Johnson, Patrick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 30, 2004 5:12 PM
Subject: [Nant-users] task
> I'm attempting to use the task. I fail out with a message of:
>
>
>
> Unabl
Have you copied *.dll files from NAntcontrib to NAnt\bin ?
Jarek
- Original Message -
From: "Nitin Agarwal" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 30, 2004 9:03 PM
Subject: [Nant-users] How to run NantContrib task
> I have downloaded the nantcontrib and built
Just ignore this. This is a known bug. Your NAnt (found in "build") is fully
functional.
Gert, can you publish a new nightly build or even a bugfix release, like:
0.84.1? I think that we've had over 20 people complaining about the same
omission.
Jarek
- Original Message -
From: "Chacon-
Some articles at MSDN (watch for long URLs)
[1]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconNETFrameworkDesignGuidelines.asp
[2]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsent7/html/vxconcodingtechniques.asp
Also, check some non-MS r
Ignore it. You have a fully functional NAnt version in "build/...". This
problem is related to the fact that we now have year 2004 while the release
includes Copyright (C) 2001-2003.
Jarek
- Original Message -
From: "Billy Bacon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday,
I'll add it.
Jarek
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Block, Jeffrey A. (Jeff)"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, January 13,
And that's exactly my problem. I cannot remove the file because mono/mcs has
problems recompiling this file since it contains (deliberately) cyclic
assembly references.
Jarek
- Original Message -
From: "Block, Jeffrey A. (Jeff)" <[EMAIL PROTECTED]>
To: "&#
Hi!
Is there any way to force re-compilation of CSharp assembly with even
though the timestamps suggests that it shouldn't get rebuilt?
Jarek
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configurati
According to the task documenation, the resulting version string is entered
in a property named "sys.version". If you want to change it, you may use the
"prefix" attribute.
I've looked at:
http://nantcontrib.sourceforge.net/nightly/help/tasks/version.html
Hope it helps.
Jarek
- Original Me
Can you send the detailed build log? Use -verbose flag on NAnt.
Jarek
- Original Message -
From: "Phalgun S Erra" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, January 07, 2004 9:59 AM
Subje
1. Have you added to the other project?
Here's the sample taken from my build:
NAnt uses precompiled NUnit using some particular version of
nunit.framework.dll. Most likely this version is not what you've compiled
your assembly against.
Try recompiling your dll, but instead of using nunit.framework.dll that
comes with NUnit, use the one from NAnt.
Hope it helps,
Jarek
Some ideas:
1. You may be running on FAT filesystem. AFAIR its timestamps are accurate
up within seconds, so you may have just hit that.
2. Your system clock may be broken. Try rebooting.
The problem with copyright in help is a known issue. Other than that, there
should be no warnings or errors.
AFAIK, there's no direct support for building *.dsw solutions.
You may want to use task on "msdev.com", like this:
For a full list of options, execute "msdev.com /?".
This isn't the best option, because it requires you to have VS6.0 installed.
Jarek
- Original Message -
From: "Wald
If you want to use a stable nant version - that can't be easily done. There
could be a solution
If you download the latest daily build, you'll see support for expressions
and functions.
Your condition can be written as:
You can get the latest nightly build at:
http://nant.sf.net/builds
Jare
Open bin/NAnt.exe.config, find:
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 31, 2003 10:55 AM
Subject: Re: [Nant-users] Trying to use NAnt with mono 0.28
>
> On Wed, 2003-12-31 at 10:21 +0100, Jaroslaw Kowalsk
Enter your nant directory (where nant.build) is located and rebuild it by
using:
$ make clean
$ make all
Your rebuilt binaries go to build/mono-1.0.unix/nant-*/bin/
Jarek
- Original Message -
From: "Philip Van Hoof" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December
> > 2) Under Windows, is there a way of adjusting how do you tell NAnt /
your
> > buildfile to target the 1.0 platform or the 1.1 platform without
adjusting
> > the .config file?
>
There are two ways:
1. Use: -defaultframework option (-k is the short form). For example:
nant -k:net-1.1 -f:aaa.bui
It's the proper way to do it, but it looks like you've made some typos:
1. a typo in "AsmIngoTags"
2. The the tag should be called "references".
I'm guessing, that because there's no "../AsmIngoTags/bin/AsmInfoTags.dll"
file, it has been removed from the fileset. To force file inclusion (and
skip
This may be a problem with SF.NET mirroring, some mirrors are more
up-to-date than others. Sometimes I get 404 when accessing some new file
from mirrors and have to retry using another one.
I suggest we never used the same file name for different releases.
Jarek
- Original Message -
Fr
This is taken from my build file. The most important are: "prefix" and
"dynamicprefix" attributes.
Resources are named:
Sooda.StubGen.Template.Template.csproj
Sooda.StubGen.Template.Template.vbproj
...
Hope it helps.
Jarek
Hi!
Quick Summary: This message discusses changes that are going to be made to
NAnt, which may break your build files in future releases. Before we make
it, we'd like to hear your opinion on the subject
As you may know, there's an ongoing effort to implement expression evaluator
for NAnt. We'll b
1. http://nant.sourceforge.net/help/introduction/fog41.html
This contains instructions for downloading NAnt.
2. http://nant.sourceforge.net/help/fundamentals/index.html
This document explains main concepts (tasks, targets, properties)
3. After downloading, take a look at files in "examp
ssage -
From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
To: "Morris, Jason" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Sunday, December 07, 2003 12:20 PM
Subject: Re: [Nant-users] Trying to auto increment my build number
> Maybe this will solve yo
Maybe this will solve your problem instead (using flat file instead of xml):
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01256.html
Jarek
- Original Message -
From: "Morris, Jason" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 07, 2003 9:48 AM
Subject: [Nant-use
I'm also having similar problems with nant schema. I couldn't get it to work
using the method you described.
There's a workaround: if you add the schema to the same project (maybe just
the same solution - I don't remember) as your build files - the intellisense
works (more or less - the schema is n
Hi!
Here's the first test release of the expression evaluator I'm developing for
NAnt.
I encourage everyone to try it. I'd like to get as much feedback as possible
on it.
Please report:
1. Does it work for you? Bug reports are welcome.
2. Is it useful?
3. Do you find the syntax simple enough? A
Every time I see constructs like this I want to scream for the support of
simple expression evaluator, because without them NAnt syntax gets uglier
every time someone invents a potentially useful extension.
MSBuild has a very simple EE here, and I think it's a good idea to support
it too.
I think
1 - 100 of 136 matches
Mail list logo
