Hello all,
after browsing the developer list's archive for some discussions about
licensing, I felt like contributing one or two thoughts. I hope nobody
minds my entering the discussion, although I just started using nant,
with no code contributions so far.
1) I feel that one major point was not
David,
You are correct, the nantschema task is under construction, and incomplete. I am
working
on getting it back into shape to support collections and nested elements. It will get
done after I'm finished with the new userdoc stuff (which is really close).
I'm more than happy to hear about any
more documentation = good... holes in docuementation = !good
I like good. Anyone want to volunteer? ;)
quote who=Martin Aliger
Hi all,
I notice that our current docs do not say anything about nant.exe.config. I
this there should be section about it discussing frameworks settings,
+1 for that idea.
-Original Message-
From: Matthew Mastracci [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 5:15 PM
To: Nant-Developers (E-mail)
Subject: [nant-dev] touch task w/non-existant files
Should the touch task create a non-existant file? The documentation
says
John,
Thanks for taking up this task...any further progress on releasing the
first beta or release candidate?
My vote would be for one distribution package with the binaries for each
.NET framework in separate directories. I don't think that we should
include the documentation or source in the
Hello Jason,
MJ My vote would be for one distribution package with the binaries for each
MJ .NET framework in separate directories. I don't think that we should
MJ include the documentation or source in the distribution package. We
MJ should instead, direct users to the website for
That is a negative Jason. We will always distribute source with our binaries. We will
also always include help/documentation.
We will also not distribute multiple, and redundant, binaries. There is no reason to
distribute 1.0 and 1.1 compiled versions of nant.
Our goal is to support all .net
The [FileSet] attribute used to describe a BuildElement (nested xml element in a task
or
datatype) is going to be removed soon. It is a relic of the days before the generic
BuildElement and provide no extra information at this point. If you are developing
tasks
please replace any [FileSet(name)]
Ok...just seemed to be some questions on what to include in the
distribution package.
Looks like Scott is firm on having source (and others are too) and one
set of binaries for the package.
No worries...just looking forward to the .8.4.0 release.
Jason
-Original Message-
From: [EMAIL
I'm not sure if this was posted to these lists before, but this registry
modification with allow you to edit .build file with nice XML syntax
hiliting in VS.NET 2003.
Windows Registry Editor Version 5.00
You can also set this by right-clicking on a .build file in a project
(add one to a project temporarily if you need to) and choosing Open
With... Choose HTML/XML Editor and click Set as Default.
-Original Message-
From: Matthew Mastracci [mailto:[EMAIL PROTECTED]
Sent: Thursday,
You can also set this by right-clicking on a .build file in a project
(add one to a project temporarily if you need to) and choosing Open
With... Choose HTML/XML Editor and click Set as Default.
File associations are cool, but the really neat trick is to get
tag-completion for NAnt scripts in
12 matches
Mail list logo
