from:"Matthew Mastracci"

Just as an extra note-
Before the change, there were 13 regex comparisons in one of our 
projects.

The change reduces this to 128000 string comparisons (taking less than 
1% of the time) and 2000 regex comparisons (taking the remaining 60% of 
the time).  Note that all numbers are approximate from profiling- you 
can use nprof to get some of your own if you wish.

I'm considering adding regex compilation to the mix, avoiding some of 
the Regex.Match overhead (since the regexes should only be compiled once 
for a single build file).  I'm not certain if the overhead of compiling 
regexes would overwhelm the savings, but I'm more confident now that the 
majority of generated regular expressions (ie: filesets passed to 
subtasks) are now simple regular expressions.

The remaining regular expressions are likely the ones passed by the 
build file author themselves, along with some of the built-in ones like 
**/CVS/**, etc.  If we cache the compiled

Matt.
Matthew Mastracci wrote:
I just checked in a change to fileset scanning that eliminates a large 
chunk of time (checked via profiling) during many of the common NAnt 
operations.

One of the biggest losers on the profiling run was Regex.Match(), called 
many, many times during a build.  The new code replaces a good 
proportion of these with CompareInfo.Compare() calls, reducing the 
overhead dramatically.

Instead of converting all  includes to regexes, the new code 
will only convert those that actually contain wildcards.

Matt.
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital 
self defense, top technical experts, no vendor pitches, unmatched 
networking opportunities. Visit www.blackhat.com

---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Fileset scanning speed-ups in CVS

Scott Hernandez wrote:
Good work. That is one that needed to be optimized :)
Do you have profiler stats/results on other most called, or time most spent
in, functions? It would be good to list them so anyone out there could step
up to challenge themselves with optimizing those functions. Just an idea...
 

Unfortunately, I haven't hooked up the "copy to clipboard" functionality 
in nprof, so all I can provide is a screenshot.  ;)

I can probably summarize the trouble spots by hand- the NAnt-bootstrap 
build would be a good candidate.  My goal right now is to catch the 
low-hanging fruit for a general  build to match (or exceed) 
VS.NET's compilation speed wherever possible.

Matt.
- Original Message ----- 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>

 

I just checked in a change to fileset scanning that eliminates a large
chunk of time (checked via profiling) during many of the common NAnt
operations.
One of the biggest losers on the profiling run was Regex.Match(), called
many, many times during a build.  The new code replaces a good
proportion of these with CompareInfo.Compare() calls, reducing the
overhead dramatically.
Instead of converting all  includes to regexes, the new code
will only convert those that actually contain wildcards.
   

 


begin:vcard
fn:Matthew Mastracci
n:Mastracci;Matthew
org:aclaro Softworks, inc.
adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada
email;internet:[EMAIL PROTECTED]
title:Software Developer
tel;work:(403) 299-6612
x-mozilla-html:FALSE
url:http://www.aclaro.com
version:2.1
end:vcard

[nant-dev] Fileset scanning speed-ups in CVS

I just checked in a change to fileset scanning that eliminates a large 
chunk of time (checked via profiling) during many of the common NAnt 
operations.

One of the biggest losers on the profiling run was Regex.Match(), called 
many, many times during a build.  The new code replaces a good 
proportion of these with CompareInfo.Compare() calls, reducing the 
overhead dramatically.

Instead of converting all  includes to regexes, the new code 
will only convert those that actually contain wildcards.

Matt.
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Projects and current working directory

Something that changed in the last six months or so (perhaps longer?) is 
that the projects no longer set their working directory equal to the 
base directory of the project itself.

I'm proposing the following patch to Project.cs to fix this.  Since I 
don't know if anyone relies on the current, strange behaviour, I'm 
posting this here for discussion.

I know that Project.GetFullPath() is supposed to handle this stuff, but 
I believe there might be a few cases within NAnt where it isn't handled 
properly (ie: paths are taken literally, rather than using 
Project.GetFullPath).  I know my  compiles take longer with 
this disabled, but I haven't yet determined what the problem is.

--- Project.cs  24 May 2004 18:03:38 -  1.71
+++ Project.cs  5 Jul 2004 22:36:36 -
@@ -882,8 +882,12 @@
 public bool Run() {
 Exception error = null;
 DateTime startTime = DateTime.Now;
+string oldDirectory = Directory.GetCurrentDirectory();
 try {
+// change to the base directory of the project before 
running anything
+Directory.SetCurrentDirectory(BaseDirectory);
+
 OnBuildStarted(this, new BuildEventArgs(this));
 Log(Level.Info, "Buildfile: {0}", BuildFileUri);

@@ -917,6 +921,9 @@
 // signal build failure
 return false;
 } finally {
+// restore the old directory
+Directory.SetCurrentDirectory(oldDirectory);
+
 string endTarget;
 if (error == null) {

---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.Console NAnt.Console.exe.config,1.58,1.59

You're right - it is braindead.
It works if you only specify a single component to license, otherwise it 
fails.  :(

What I didn't realize is that it will try over and over to re-populate 
its hashtable, failing.  This causes the assembly resolution to fail. 
Unfortunately, there isn't any way to call lc.exe multiple times.

We should probably be documenting some of these quirks somewhere.  I 
usually end up running into something that looks like a bug, but turns 
out to be "by design".

Matt.
Matthew Mastracci wrote:
Gert Driesen wrote:
Matthew,
The .NET 1.1 lc.exe indeed has a command line switch for specifying 
assembly
references, but it doesn't work.  That's why we don't use it.
 

Actually, it does and I have proof.  :)  The only thing is that you 
can't specify assemblies that exist in the GAC (it gives you various 
errors from having the same key twice in a hashtable).

Basically, it works for me and I can see exactly why given the 
decompiled source.

Using Reflector:
   handler1 = new 
ResolveEventHandler(LicenseCompiler.OnAssemblyResolve);
   AppDomain.CurrentDomain.AssemblyResolve += handler1;
   context1 = new DesigntimeLicenseContext();

and in OnAssemblyResolve
...
 foreach (string text2 in LicenseCompiler.assemblies)
 {
   assembly1 = Assembly.LoadFrom(text2);
   if (assembly1 == null)
   {
 return null;
   }
   text3 = assembly1.GetName().Name;
   LicenseCompiler.assemHash.Add(text3, assembly1);
   if (text3 != text1)
   {
 continue;
   }
   return assembly1;
 }
...
Gert
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 06, 2004 2:24 AM
Subject: [nant-commits] CVS: nant/src/NAnt.Console
NAnt.Console.exe.config,1.58,1.59
 

Update of /cvsroot/nant/nant/src/NAnt.Console
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8787
Modified Files:
NAnt.Console.exe.config
Log Message:
lc.exe supports assembly references
Index: NAnt.Console.exe.config
===
RCS file: /cvsroot/nant/nant/src/NAnt.Console/NAnt.Console.exe.config,v
retrieving revision 1.58
retrieving revision 1.59
diff -C2 -d -r1.58 -r1.59
*** NAnt.Console.exe.config 5 Jul 2004 18:11:21 - 1.58
--- NAnt.Console.exe.config 6 Jul 2004 00:24:11 - 1.59
***
*** 153,156 
--- 153,157 
 
 lc
+ 
  
name="supportsassemblyreferences">true
 

 
 

---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
nant-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-commits
  

 



---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: ResGen assembly references?

Gert Driesen wrote:
Can't we do a quick parse of the resx sources to see if they require
those references ? A large number of cases do not require any references
at all.

Yeah we probably could ... Just didn't/don't have time for that, and didn't
see much need for it at that point ...
I had to comment it out here because it was taking up to ten seconds to 
compile each .resx file in the solution.

BTW- could we just skip copying resources and compile the .resx files 
after we copy references?  I'm assuming that VS.NET would be compiling 
the .resx file using only the "Copy Local" references anyways, so we 
wouldn't be doing anything differently.

I'm working on cutting down the time for a  build in our
shop again (via profiling)- this is one of the biggest culprits right
now.  :)
I understand, but we can't sacrifice features for performance.
But on the other hand we shouldn't slow down *every*  solution based
build in order to satisfy some corner cases if we can avoid doing so.

No ofcourse not, if we can combine performance and features, I'm all for it
;-)
This is a really big performance drain for any build that uses 
references extensively.  I'd say it's a good candidate for performance 
tuning.  :)

Matt.
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.Console NAnt.Console.exe.config,1.58,1.59

Gert Driesen wrote:
Matthew,
The .NET 1.1 lc.exe indeed has a command line switch for specifying assembly
references, but it doesn't work.  That's why we don't use it.
 

Actually, it does and I have proof.  :)  The only thing is that you 
can't specify assemblies that exist in the GAC (it gives you various 
errors from having the same key twice in a hashtable).

Basically, it works for me and I can see exactly why given the 
decompiled source.

Using Reflector:
   handler1 = new 
ResolveEventHandler(LicenseCompiler.OnAssemblyResolve);
   AppDomain.CurrentDomain.AssemblyResolve += handler1;
   context1 = new DesigntimeLicenseContext();

and in OnAssemblyResolve
...
 foreach (string text2 in LicenseCompiler.assemblies)
 {
   assembly1 = Assembly.LoadFrom(text2);
   if (assembly1 == null)
   {
 return null;
   }
   text3 = assembly1.GetName().Name;
   LicenseCompiler.assemHash.Add(text3, assembly1);
   if (text3 != text1)
   {
 continue;
   }
   return assembly1;
 }
...
Gert
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 06, 2004 2:24 AM
Subject: [nant-commits] CVS: nant/src/NAnt.Console
NAnt.Console.exe.config,1.58,1.59
 

Update of /cvsroot/nant/nant/src/NAnt.Console
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8787
Modified Files:
NAnt.Console.exe.config
Log Message:
lc.exe supports assembly references
Index: NAnt.Console.exe.config
===
RCS file: /cvsroot/nant/nant/src/NAnt.Console/NAnt.Console.exe.config,v
retrieving revision 1.58
retrieving revision 1.59
diff -C2 -d -r1.58 -r1.59
*** NAnt.Console.exe.config 5 Jul 2004 18:11:21 - 1.58
--- NAnt.Console.exe.config 6 Jul 2004 00:24:11 - 1.59
***
*** 153,156 
--- 153,157 
 
 lc
+ 
   

name="supportsassemblyreferences">true
 

 
 

---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
nant-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-commits
   

 


begin:vcard
fn:Matthew Mastracci
n:Mastracci;Matthew
org:aclaro Softworks, inc.
adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada
email;internet:[EMAIL PROTECTED]
title:Software Developer
tel;work:(403) 299-6612
x-mozilla-html:FALSE
url:http://www.aclaro.com
version:2.1
end:vcard

Re: [nant-dev] Re: ResGen assembly references?

Can anyone give me a hint on how to create these assembly references in 
1.0/1.1 via VS.NET?  I haven't seen them before.

Gert Driesen wrote:
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Matthew Mastracci" <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Tuesday, July 06, 2004 8:25 AM
Subject: Re: [nant-dev] Re: ResGen assembly references?

Gert Driesen wrote:

- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Matthew Mastracci" <[EMAIL PROTECTED]>
Cc: "Gert Driesen" <[EMAIL PROTECTED]>
Sent: Tuesday, July 06, 2004 3:13 AM
Subject: Re: ResGen assembly references?
<>Matthew Mastracci wrote:

After upgrading to the latest CVS version, I've found that the
 task is taking a long time to run for each project because it
seems to be copying all of the project references.

These are necessary, as resx files can contain references to types in the
project references.  So  need to be able to instantiate these

types.

What's the reason for this behaviour?  We've never needed it before
and it increases our build time dramatically.  I don't think the 1.0
or 1.1  tasks can even utilize assembly references.

We didn't need it as we didn't implement this yet.  The resgen.exe tool

for

the .NET 1.0 and .NET 1.1 does not provide direct support for assembly
references, but you can trick it into the by copying the tool itself, and
all assembly references to the same (temporary) directory, and launching

the

tool from there.  This is what we do for .NET 1.0 and .NET 1.1.  For .NET
2.0 we just specify the assembly references on the command line.

Can't we do a quick parse of the resx sources to see if they require
those references ? A large number of cases do not require any references
at all.

Yeah we probably could ... Just didn't/don't have time for that, and didn't
see much need for it at that point ...

I'm working on cutting down the time for a  build in our
shop again (via profiling)- this is one of the biggest culprits right
now.  :)

I understand, but we can't sacrifice features for performance.

But on the other hand we shouldn't slow down *every*  solution based
build in order to satisfy some corner cases if we can avoid doing so.

No ofcourse not, if we can combine performance and features, I'm all for it
;-)
Gert

begin:vcard
fn:Matthew Mastracci
n:Mastracci;Matthew
org:aclaro Softworks, inc.
adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada
email;internet:[EMAIL PROTECTED]
title:Software Developer
tel;work:(403) 299-6612
x-mozilla-html:FALSE
url:http://www.aclaro.com
version:2.1
end:vcard

[nant-dev] task for NAnt :)

2004-04-05 Thread Matthew Mastracci

or, "when Microsoft went open-source."

Looks like Microsoft has finally jumped on the true "open source" 
bandwagon with the release of WiX - an XML to MSI compiler.

It's unfortunately not under a GPL-compatible license (preventing direct 
linking), but the command-line interface would work just fine for most 
purposes, I believe.

An installer-builder (an alternative to NSIS) would certainly be a 
useful tool to help round-out the NAnt toolset.

See here for more info:
http://blogs.msdn.com/robmen
Matt.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] CopyLocal - once and for all :)

2004-03-18 Thread Matthew Mastracci

Gert Driesen wrote:

Matthew,

The CopyLocal behaviour depends on whether the assembly is a system
assembly or not (and some other criteria too perhaps). 

I'm pretty sure the current implement matches the behaviour of VS.NET
2003, but I might be wrong ofcourse.
Do you have a example of where the behaviour differs ?
I wonder if this is the problem: in Reference.cs, _privateSpecified and 
_isPrivate are being used before they have actually been assigned in the 
constructor (for project refs and visual C++ projects references).

The ternary operator logic is correct, but I think _copyLocal always 
ends up being true for project references due to this bug.  I suppose 
the solution is to move the test up in the file.

This will likely fix my issue.  :)

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] CopyLocal - once and for all :)

2004-03-18 Thread Matthew Mastracci

It seems like our CopyLocal logic in the  task doesn't seem to 
match VS.NET 2003.  Did this change between 2002/2003?

As far as I can see, if the CopyLocal flag is not specified in 2003, it 
should be treated as false.  Does anyone know for sure what this is in 2002?

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: Solution task fixes + speedups

2004-03-18 Thread Matthew Mastracci

Gert Driesen wrote:

So anyways, I finally understand that you are correct - VS.NET does
check AssemblyFolders before HintPath.  IMHO this is a strange way to do
things.  VS.NET doesn't make it easy to easily reproduce a build between
two machines, does it?
No, definitely not.  In my opinion, VS.NET should only use AssemblyFolders
if the AssemblyFolderKey is set on the reference.
I agree!  :)

Unfortunately, I need to build on a clean system that doesn't have any
csproj.user files.  Perhaps I'll just delete the AssemblyFolders key
from the registry on the build machine.
Kind of drastic, no ?
Since the AssemblyFolder stuff doesn't take into account versioning (we 
use two different versions of the ComponentOne stuff and need both for a 
successful build), we need to be able to specify the exact version that 
we're linked against.  C1 is an example of a 3rd party library that 
can't be upgraded from a specific version without *something* breaking.  :)

We also can't really check in the csproj.user file, since each developer 
has their own copy (it's not really meant to be checked in anyways).

Do you have time to add support for the ReferencesPath attrribute to our
reference resolving procedure ?
Do you mean reading the csproj.user files?  Sure.

I suppose we should probably add in some debugging traces for reference 
resolution.  It would make it easier to figure out why a DLL is getting 
picked up from the wrong place.

I really would like to set up a small team of developers to focus on
improving/refactoring the  task, would you be interested ?
Yep.  Just let me know and I'll see if I can allocate a bit of time to 
help out.

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote:

I can also guarantee 100% that VS.NET (2003) is only using the hintpath as a
last resort ;)
I've reverted the change in CVS.  Thanks for the explanation  :)

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote:

Matthew,

I can also guarantee 100% that VS.NET (2003) is only using the hintpath as a
last resort ;)
The actual order is :

1. the project directory (at least this is what MS says, but I doubt this)
2. The ReferencesPath (as stored in the user options file, eg.
.csproj.user)
3. The .NET Framework directory
4. The AssemblyFolder (even if the AssemblyFolderKey is not specified on the
reference itself)
5. The HintPath
Please send me a repro to convince me otherwise, but make sure you first
check if you don't have entries in the ReferencesPath attribute in the .user
file :)
Oh - you're right, I had a bunch of reference paths in the project's 
.user file.  I deleted my .user file and ended up with the same 
behaviour.  Looks like VS.NET is ignoring the HintPath in this case and 
just using the AssemblyFolder version of the .DLL.

So anyways, I finally understand that you are correct - VS.NET does 
check AssemblyFolders before HintPath.  IMHO this is a strange way to do 
things.  VS.NET doesn't make it easy to easily reproduce a build between 
two machines, does it?

Unfortunately, I need to build on a clean system that doesn't have any 
csproj.user files.  Perhaps I'll just delete the AssemblyFolders key 
from the registry on the build machine.

Sorry for doubting.  ;)

Matt.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Solution task fixes + speedups

Matthew Mastracci wrote:

If you want to revert the ordering, please wrap the assembly folder 
stuff with a check for the "AssemblyFolderKey = blah" attribute of the 
reference.  AFAIK, if this attribute is missing, VS.NET ***will not*** 
use the AssemblyFolders for resolution.
Just to clarify, I think the change should be this (pseudo-patch):

private bool ResolveFromAssemblyFolders(XmlElement referenceElement) {
-  if (referenceElement.Attributes["AssemblyFolderKey"] != null) {
+  if (referenceElement.Attributes["AssemblyFolderKey"] == null) {
+  return;
+  } else {
   string assemblyFolderKey = 
referenceElement.Attributes["AssemblyFolderKey"].Value;

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: Solution task fixes + speedups

I can absolutely, 100% guarantee that this is the case.  I have a 
.csproj file with the following reference:


The DLL in the HintPath is of version 1.1.20024.78.  When I compile with 
VS.NET, the DLL that ends up in the bin directory is version 1.1.20024.78.

There is also an AssemblyFolder entry that looks like this:

C1Studio = C:\Program Files\ComponentOne Studio.NET\bin

In this directory is C1.Win.C1FlexGrid.dll version 2.1.20034.144.  This 
is not the DLL we want to compile against.

If you want to revert the ordering, please wrap the assembly folder 
stuff with a check for the "AssemblyFolderKey = blah" attribute of the 
reference.  AFAIK, if this attribute is missing, VS.NET ***will not*** 
use the AssemblyFolders for resolution.

Does this sound acceptable?  It looks like with this logic, I should be 
able to compile my project (while keeping your resolution order intact).

Gert Driesen wrote:

Matthew,

I looked into this again, and I'm pretty sure I'm right :

The HintPath is definitely the "last resort" for VS.NET.  So we should undo
your change (unless you can send me a repro).
The issue you encountered was probably due to the fact that we don't yet use
the path list in the ReferencesPath attribute (of the Settings node) in the
.user file (the project user options) to locate assemblies. (feel free to
add support for this to the solution task :-))
Gert
----- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, March 16, 2004 11:35 PM
Subject: [nant-dev] Re: Solution task fixes + speedups



Gert Driesen wrote:


But you actually have two different "assembly folders" : you have the
assembly folder that is referenced in your project file using the
"AssemblyFolderKey" attribute of the  element, eg.
...


and you have the rest of the AssemblyFolder registry keys.  Perhaps
VS.NET

first checks the AssemblyFolderKey, then the HintPath and then the rest
of

the assembly folders.  But I'm just guessing here.
Aha...  I don't have an AssemblyFolderKey attribute on my reference -
it's a direct file reference.  The AssemblyFolder check was still
picking it up, however.
Perhaps the order was correct as you had it, but we should skip the
assembly folder check if that attribute is missing.

Even if Microsoft describes it as a last resort, it's definitely not how
VS.NET does it.


I'll verify it tomorrow, and report it to MS if necessary
Cool.  Thanks!

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers





---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: NAnt pedantic mode

Gert Driesen wrote:

You mean an attribute that didn't exist ?  Properties that don't exist cause
a build error already ...
Yep - that's what I was thinking.

But I agree that we should indeed have this mode (or just always run NAnt in
this mode, what do you propose) ...
In what cases should NAnt throw a build error :

- a system property that no longer exist
- an attribute/child element that is deprecated, and the IsError property of
the ObsoleteAttribute is set to true
- a task/type that is deprecated, and the IsError property of the
ObsoleteAttribute is set to true
- an attribute/child element that does not (or no longer) exist
+1 on all four.  AFAIK, 2 and 3 are already done.

in what cases should NAnt output a warning (deprecated message) in the build
log :
- a system property that has been replaced/renamed (eg. replaced by a
function), but the original property still exists.
- an attribute/child element that is deprecated, and the IsError property of
the ObsoleteAttribute is set to false
- a task/type that is deprecated, and the IsError property of the
ObsoleteAttribute is set to false
+1 on all three here too.

Please correct me wherever necessary and add items to these lists 
Looks good to me.  The biggest issue I run into is renamed attributes. 
Renamed sub-elements could also end up being a bit of a problem.

Should this be the default mode?  I'm not sure about this one, but we 
would need a way to run in "less-strict" mode.

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt pedantic mode

I've run into a number of build-script bugs today that are related to 
NAnt task properties changing/disappearing/obsoleting/etc.

What does everyone think of a command-line flag to put NAnt into 
pedantic mode?  This would throw an error if any build task tried to use 
a property that didn't exist or was obsoleted.

I would personally run in pedantic mode all the time.

Ideas?  Comments?  Flames?  :)

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Change to "call" task makes upgrade difficult

James C. Papp wrote:

This was also my rational of not just adding a flag to . The 
task is just a dynamic form of the  task's depends attribute..., in
all other respect their ultimate functionality would be identical.  The
 task was not meant to be used as a way to call targets, but (more
accurately), to assert that a set of dependencies were meet or handled (if
needed) before continuing. This is similar a little bit to .NET security with
the way you can request certain privileges up front (as assembly metadata), or
dynamically by asserting them within code.
Heh...  I just ran into the same problem you have.  My workaround so far 
is to add the following attribute to all of my "execute-once" targets:

unless="${target::has-executed(target::get-current-target())}"

I would love to have the  task instead.  :)

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote:

But you actually have two different "assembly folders" : you have the
assembly folder that is referenced in your project file using the
"AssemblyFolderKey" attribute of the  element, eg.
...

and you have the rest of the AssemblyFolder registry keys.  Perhaps VS.NET
first checks the AssemblyFolderKey, then the HintPath and then the rest of
the assembly folders.  But I'm just guessing here.
Aha...  I don't have an AssemblyFolderKey attribute on my reference - 
it's a direct file reference.  The AssemblyFolder check was still 
picking it up, however.

Perhaps the order was correct as you had it, but we should skip the 
assembly folder check if that attribute is missing.

Even if Microsoft describes it as a last resort, it's definitely not how
VS.NET does it.


I'll verify it tomorrow, and report it to MS if necessary
Cool.  Thanks!

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Solution task fixes + speedups

Gert Driesen wrote:

3.  The HintPath for a reference is now checked before the
AssemblyFolders.  VS.NET checks it this way and it can break a solution
that wants to reference (using a direct assembly reference) a different
version of an assembly than might have been installed in an
AssemblyFolder path.
Are you sure about this ???  I haven't checked this, but according to MS
this is kind of "the last resort" ...
Guaranteed.  I have a project that references an assembly (v1 of the 
DLL) with the same name as an assembly in one of my assembly folders (v2 
of the DLL).  Before my change, it was incorrectly picking up v2.  After 
the change, it correctly picks up v1.

Even if Microsoft describes it as a last resort, it's definitely not how 
VS.NET does it.

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Solution task fixes + speedups

I've spent a bit more time speeding up the solution task and fixing 
differences from VS.NET.  Here's a short summary of what to expect with 
the latest CVS:

1.  We only create one AppDomain per solution build and per project 
build.  We were creating dozens of AppDomains per project build before.

2.  GAC checks (IsAssemblyInGac) are now cached per solution build. 
This cuts 25% of the build time off alone.

3.  The HintPath for a reference is now checked before the 
AssemblyFolders.  VS.NET checks it this way and it can break a solution 
that wants to reference (using a direct assembly reference) a different 
version of an assembly than might have been installed in an 
AssemblyFolder path.

Matt.

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: Remove support for WebDAV from task ?

2004-03-08 Thread Matthew Mastracci

AFAIK, VS.NET uses front page extensions to talk to the webserver.  I
think I chose webdav when I first looked at it because it offers that as
an alternative when it can't open the solution w/FPE.

FPE seems to get around the permissions issue better than WebDAV does. 
They've probably got some good hacks in there to make sure the whole
thing is painless.  Unfortunately, front-page extensions are barely
documented - I couldn't find a suitable reference to base an
implementation off.  

This was all before the  element made this stuff
less-than-useful, of course.  :)

The more I think about it, the more I am in favour of just trashing the
WebDAV stuff.  Does anyone *really* need to build a project on a remote
webserver?  If so, we can always provide a workaround by HTTP GETing the
source and WebDAV putting the binaries, I suppose.

Matt.

On Mon, 2004-03-08 at 22:33, Gert Driesen wrote:
> Matthew, can you tell me what makes our WebDAV access to IIS so much more
> troublesome, than what VS.NET uses ?
> 
> Thanks,
> 
> Gert
> ----- Original Message - 
> From: "Matthew Mastracci" <[EMAIL PROTECTED]>
> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, March 09, 2004 1:04 AM
> Subject: [nant-dev] Re: Remove support for WebDAV from  task ?
> 
> 
> The latest stuff has the EnableWebDAV stuff to prevent it being used by
> default.  It's been in there for a month or so and tells the user to
> either provide a webmap or set EnableWebDAV = true to make it work.
> 
> -1 for removing it - if people want it, they can be pointed at
> documentation to set up the server properly.
> 
>  /// 
>  /// Allow the task to use WebDAV for retrieving/compiling the
> projects within solution.  Use of
>  ///  is preferred over WebDAV.  The
> default is .
>  /// 
>  /// 
>  /// WebDAV support requires permission changes to be
> made on your project server.  These changes may affect
>  /// the security of the server and should not be applied to
> a public installation.
>  /// Consult your web server or the NAnt Wiki
> documentation for more information.
>  /// 
>  [TaskAttribute("enablewebdav", Required = false)]
>  [BooleanValidator()]
>  public bool EnableWebDAV {
>  get { return _enableWebDAV; }
>  set { _enableWebDAV = value; }
>  }
> 
> 
> Jaroslaw Kowalski wrote:
> 
> > 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"
> > <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
> > <[EMAIL PROTECTED]>
> > Sent: Monday, March 08, 2004 11:47 PM
> > Subject: RE: [nant-dev] Remove support for WebDAV from  task ?
> >
> >
> >
> >>I haven't used WebDAV, but if I could use it to distribute a website to a
> >
> > final server, it would be very very useful to me. At the moment, I have a
> > manual FTP step is required to move a web project to the production
> server.
> >
> >>Erick
> >>
> >>
> >>>-Original Message-
> >>>From: [EMAIL PROTECTED]
> >>>[mailto:[EMAIL PROTECTED] Behalf Of Gert
> >>>Driesen
> >>>Sent: Monday, March 08, 2004 2:36 PM
> >>>To: NAnt Users Mailing List; Nant-Developers (E-Mail)
> >>>Subject: [nant-dev] Remove support for WebDAV from  task ?
> >>>
> >>>
> >>>Hi,
> >>>
> >>>I'm just asking to get an idea of how many people actually
> >>>use it, but how
> >>>would you feel if we would remove WebDAV support from the
> >>> task ?
> >>>
> >>>We've noticed that lots of people have problems configuring
> >>>their webserver,
> >>>in order to get the  task working, so it might be
> >>>better to remove
> >>>support for WebDAV altogether.  This would also allow us to
> >>>simplify some of
> >>>the code, and make the code easier to maintain.
> >>>
> >>>What do you think ?
> >>>
> >>>Gert
> >>>
> >>>
> >>>
> >>>-

[nant-dev] Re: Remove support for WebDAV from task ?

2004-03-08 Thread Matthew Mastracci

On second thought, it may be beneficial to break out the WebDAV stuff 
into a separate  task.

I'm not sure if people are relying on being able to build code via 
WebDAV shares, however.  Perhaps the solution task could use WebDAV via 
the alternate task, rather than the internal WebDAV stuff?

Anyways, I'll say 0 instead of -1 for removal of WebDAV.  I'm not 
personally convinced either way, but I do agree it's a huge pain in the 
butt to get it configured (besides being a security hole).

Matt.

Matthew Mastracci wrote:

The latest stuff has the EnableWebDAV stuff to prevent it being used by 
default.  It's been in there for a month or so and tells the user to 
either provide a webmap or set EnableWebDAV = true to make it work.

-1 for removing it - if people want it, they can be pointed at 
documentation to set up the server properly.

/// 
/// Allow the task to use WebDAV for retrieving/compiling the 
projects within solution.  Use of
///  is preferred over WebDAV.  The default 
is .
/// 
/// 
/// WebDAV support requires permission changes to be 
made on your project server.  These changes may affect
/// the security of the server and should not be applied to 
a public installation.
/// Consult your web server or the NAnt Wiki 
documentation for more information.
/// 
[TaskAttribute("enablewebdav", Required = false)]
[BooleanValidator()]
public bool EnableWebDAV {
get { return _enableWebDAV; }
set { _enableWebDAV = value; }
}

Jaroslaw Kowalski wrote:

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"
<[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Monday, March 08, 2004 11:47 PM
Subject: RE: [nant-dev] Remove support for WebDAV from  task ?


I haven't used WebDAV, but if I could use it to distribute a website 
to a


final server, it would be very very useful to me. At the moment, I have a
manual FTP step is required to move a web project to the production 
server.

Erick


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gert
Driesen
Sent: Monday, March 08, 2004 2:36 PM
To: NAnt Users Mailing List; Nant-Developers (E-Mail)
Subject: [nant-dev] Remove support for WebDAV from  task ?
Hi,

I'm just asking to get an idea of how many people actually
use it, but how
would you feel if we would remove WebDAV support from the
 task ?
We've noticed that lots of people have problems configuring
their webserver,
in order to get the  task working, so it might be
better to remove
support for WebDAV altogether.  This would also allow us to
simplify some of
the code, and make the code easier to maintain.
What do you think ?

Gert



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&opÌk
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click





---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Remove support for WebDAV from task ?

2004-03-08 Thread Matthew Mastracci

The latest stuff has the EnableWebDAV stuff to prevent it being used by 
default.  It's been in there for a month or so and tells the user to 
either provide a webmap or set EnableWebDAV = true to make it work.

-1 for removing it - if people want it, they can be pointed at 
documentation to set up the server properly.

/// 
/// Allow the task to use WebDAV for retrieving/compiling the 
projects within solution.  Use of
///  is preferred over WebDAV.  The 
default is .
/// 
/// 
/// WebDAV support requires permission changes to be 
made on your project server.  These changes may affect
/// the security of the server and should not be applied to 
a public installation.
/// Consult your web server or the NAnt Wiki 
documentation for more information.
/// 
[TaskAttribute("enablewebdav", Required = false)]
[BooleanValidator()]
public bool EnableWebDAV {
get { return _enableWebDAV; }
set { _enableWebDAV = value; }
}

Jaroslaw Kowalski wrote:

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"
<[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Monday, March 08, 2004 11:47 PM
Subject: RE: [nant-dev] Remove support for WebDAV from  task ?



I haven't used WebDAV, but if I could use it to distribute a website to a
final server, it would be very very useful to me. At the moment, I have a
manual FTP step is required to move a web project to the production server.
Erick


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gert
Driesen
Sent: Monday, March 08, 2004 2:36 PM
To: NAnt Users Mailing List; Nant-Developers (E-Mail)
Subject: [nant-dev] Remove support for WebDAV from  task ?
Hi,

I'm just asking to get an idea of how many people actually
use it, but how
would you feel if we would remove WebDAV support from the
 task ?
We've noticed that lots of people have problems configuring
their webserver,
in order to get the  task working, so it might be
better to remove
support for WebDAV altogether.  This would also allow us to
simplify some of
the code, and make the code easier to maintain.
What do you think ?

Gert



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&opÌk
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Matthew Mastracci

Giuseppe Greco wrote:

As a curiousity, wouldn't you be able to use a regular target and
properties to define what to call?  For instance, your gateway project
can just do this:

Yes, but this is exactly what I'm trying to avoid...

When a master build file contains more than 3 or 4 targets
to forward, you have to define lots of properties just to handle that.
I think a wild target would be much more elegant. Furthermore,
be able to define a wild target that is executed when the user
specifies a target that does not exist in the current build file,
would be handy...
Of course, that's nothing vital, but...
Sorry.  :)  I just noticed your first post, describing exactly what I 
put in my message here.

I suppose it's good for allowing you to specify targets for your 
subprojects without having to know about them in your master build file. 
   Would you be rewriting your master to use wildcards as well?

Matt.

---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Matthew Mastracci

As a curiousity, wouldn't you be able to use a regular target and 
properties to define what to call?  For instance, your gateway project 
can just do this:

   
 
   
 
   
   
 
   
   
 
   
 
   
The master just needs to set the "operation" property before calling. 
I'm not certain these wildcard targets are necessary in this case.



etc...

Giuseppe Greco wrote:

Hi all,

I've just completed the implementation of the
stuff we discussed yesterday.
Right now I'm out of office and I don't have
CVS access due to proxy restrictions, so
attached to this email you will find the
modified files. I'll send you a patch tomorrow.
The modified files are:

NAnt.Core/Project.cs
line81   added WildTarget const
line   132   added _currentTarget field
lines  410 -  416added CurrentTarget property
lines  784 -  796replaced do-while statement
lines 1415 - 1419added wild targets handling
NAnt.Core/Functions/NAntFunctions.cs
lines   83 - 98  added GetCurrentTarget functioin
These modifications allow you to specify a wild target
that is executed when the user specifies a target that
does not exist in the current build file. Here's an
example:

  

  
  

  

if you type

  nant hello

from the command, you get the message "This is the hello target".

Furthermore, using the master-gateway-slave build file pattern is
much easier (see my previous emails). Here below is another
example.
Let's start with the usual project:

/myProject
 + default.build
 + /src
 + default.build
 + /Subproject
+ default.build
+ HelloWorld.cs
the master build file (/myProject/default.build) looks
like this:



 

  
  

  
  

  


... and the gateway build file (/myProject/src/default.build)
like this:



  

  

  
  

  
  

  

  


I don't report the slave build file (/myProject/src/Subproject/default.build)
since it is like any other build file written till now.
Wild targets allow you to write more compact build files and
provide a standard way to handle unexpected targets.
What do you think about that?

j3d.


Giuseppe Greco
::agamura::

phone:  +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email:  [EMAIL PROTECTED]
web:www.agamura.com



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: touch task bug

2004-02-25 Thread Matthew Mastracci

Sure...  shouldn't be too tough.  I'll just create a testcase that runs 
the  task twice in a row on the same file.

Gert Driesen wrote:

- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>; "Nant-Developers (E-mail)"
<[EMAIL PROTECTED]>
Sent: Wednesday, February 25, 2004 9:11 PM
Subject: [nant-dev] Re: touch task bug

I've had a fix for this one locally for a while - just checked it in.

Thanks, can you also add a testcase for this ?

Gert

---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: touch task bug

2004-02-25 Thread Matthew Mastracci

I've had a fix for this one locally for a while - just checked it in.

Gert Driesen wrote:

Matt,
 
Can you please submit a bug report for this ?
 
Thanks,
 
Gert

- Original Message -
*From:* Steele, Matt 
*To:* '[EMAIL PROTECTED]'

*Sent:* Tuesday, February 24, 2004 1:06 AM
*Subject:* [nant-dev] touch task bug
The touch task creates a file but does not release it. 
On line 163 of TouchTask.cs, it should probably assign the result of
File.Create to a stream and then close the stream.  Sorry, we had
been using the touch task to create lock files, but then we couldn't
delete them!



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Build Process

2004-02-06 Thread Matthew Mastracci

There's also some info in the NAnt wiki at:

http://nant.sourceforge.net/wiki/index.php/SolutionTask

Martin Aliger wrote:
Hi,

it is in Core and documenation to this task (as well as all others) could be
found at
http://nant.sourceforge.net/nightly/help/tasks/solution.html
Martin

- Original Message - 
From: "Ron Werner" <[EMAIL PROTECTED]>
To: "Nicklas Norling" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 10:59 PM
Subject: RE: [nant-dev] Build Process



Thanks for the update.  Is the Solution Task part of the NAntContrib or
part

of the "Core" product (and where can I learn about it)?

Thanks,

Ron

-Original Message-
From: Nicklas Norling [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 3:51 PM
To: Ron Werner; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Build Process
Hi Ron.

When I looked at it a few month ago the slingshot task appeared not to be
maintained.
I think the solution task is the way to go. I use if for >30 projects/sln
and
works great.
Good luck to you!
/Nicke
- Original Message -
From: "Ron Werner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 10:31 PM
Subject: [nant-dev] Build Process


I have been working with NAnt the last couple of days, however I have
been

coming across problems with dependencies.

Is there some documentation somewhere that kind of discusses the overall
process, and the accepted standard (if there is one) on how to create a
.build file.
I have also seen some articles on Slingshot and SolutionTask.  Is
SolutionTask replacing Slingshot?  Is the following code example just
executed in an XML file:
   
   
   
   
   
   
Sorry if these are stupid questions, however I am just getting started
with

NAnt.

Thanks,

Ron






---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers




---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Nightly task docs broken

2004-01-19 Thread Matthew Mastracci

Looks like the nightly task docs broke at some point-

http://nant.sourceforge.net/nightly/help/

"You don't have permission to access /nightly/help/index.html on this 
server."

Permissions issue with SCP?

Matt.

---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: SolutionTask

2004-01-16 Thread Matthew Mastracci

Guids should be unique.  The only way to get this is by copying a 
project and forgetting to change it.  VS.NET doesn't warn you of this, 
but behaves badly in subtle ways.

Ian MacLean wrote:
Is this the right patch ? if it is possible to have two valid projects 
with an identical guid should we use a different key for the hash table 
- perhaps a combination of the guid and the projectname ?

Ian

Hi all,

I found one very annoying feature/bug of  task:

Projects (.csproj) are loaded into hashtable regarding their guid. But if
two projects with same guid are loaded, no error/warning is issued and 
one
of those projects disappears! Such projects could be created by 
copying and
renaming existing project into another file. Create new project with 
Visual
Studio generate new guid, so propability to create existing guid is
negligible.

Small patch to is attached. It checks this key violation rule and throws
BuildException when it found one.
Regards,
Martin
 



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Inter-Task XML Communication (WAS: new xml type)

2004-01-07 Thread Matthew Mastracci

Scott Hernandez wrote:

There are many places where inter-task communication would be useful. Having
the context of what is going on around a task is very interesting. I don't
know much about how msbuild works, but I get the idea this is what they are
pushing as the mechanism for tying together their tasks, and functionality.
The only problem I start to see is that there becomes a situation of
inter-dependence and a complication of context. If it gets to the point that
a task needs to know what is around it (preceding and such) to get its job
done it may get too complicated to write and test.
Yep - each task can survive on its own, but can use extra information
from other tasks to perform a more integrated task or can just provide
more information for other tasks to do the same (example eludes me at
the current moment).

*XPathObjectNavigator stuff:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnexxml/html/xml03172003.asp
http://cvs.sourceforge.net/viewcvs.py/bbooprevalence/Bamboo.Prevalence/src/Bamboo.Prevalence.XPath/
+1 for XPathObjectNavigator. I was thinking about this myself. W

The XmlSerializer stuff can create xml schema for us, is this what you mean?
Yep. I didn't know if this was possible. If so, that rocks! ;)

If each xml object could tag along an associated schema, this would
enforce the validity of the object during user manipulation of the XML
object, allowing it to be "re-imported" into the NAnt world at some
later date.

Are you saying that we would serialize these objects to disk for use by nant
during another execution, or just during the current one? What is the
application of this?
Err... that was a think-o. By "later date" I meant "later time" in the
build process. Still running on less than adequate sleep. ;)

The xml documents should be in-memory items within NAnt as you mentioned
earlier. This doesn't preclude having an or task to
persist them longer, however.

Matt.

---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: solution task

I like the ability to customize any field within the project.  Would it 
be more suitable to perform this modification using the 
/ tasks outside of the solution task itself?

Perhaps some sort of per-project handler subtask could work as well:


   ... 
  
	
		
	
  


I love the ability to do per-project customization.  The above would 
allow us to re-use some existing tasks (and perhaps perform more complex 
project manipulation!).

How does this sound?

Jaroslaw Kowalski wrote:
Some time ago I proposed a syntax to allow the ultimate customization of
 task.
It was something like:


 



 




/codepage:1250


Each  would be processed after the project is loaded into memory
and it matches the "project" attribute. The algorithm would be:
1. For each , find the XML node specified by "name" XPath attribute
2. Set the value of this node as specified in "value" attribute
The idea is simple, yet allows for ultimate extensibility. Perhaps we might
even think about adding / removing items specified by XPath.
For parameters, that aren't there in the *.csproj file we'd have special
tags, like  mentioned above.
Applications:

1. To override some flag in all C# projects, you use: 
2. To override some flag in all VB projects, you use: 
3. To override some flag in all VB projects, you use: 
4. To exclude some file from compilation, use:
 


What do you think ?

Jarke

- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, January 06, 2004 7:27 PM
Subject: [nant-dev] [Fwd: [Nprof-developers] Re: solution task]



 Original Message 
Subject: [Nprof-developers] Re: solution task
Date: Tue, 06 Jan 2004 11:09:22 -0700
From: Matthew Mastracci <[EMAIL PROTECTED]>
To: Martin Aliger <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Sounds good to me too - just ensure that you've got compilerargs
specified by language.  There's a number of flags that are valid for a
single compiler only.
Martin Aliger wrote:


Hi all !

1/
Do you think, that now is good time to some cleaning and restructuring
in solution task as we discussed earlier? I have some spare time and
appetite to do that now!
2/
Also I would need (and like to) make some improvements to that task.
What I need (and currently use not-commited patch) is need to custom
arguments override like there:

  
   
  
  
   
   
   
  
  
   
  

We previously discuss that as it will be nice to do that at solution
level or at project level. Do you still like the idea? I could implement
that if you agree with that...
Regards,
Martin


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
Nprof-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nprof-developers


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers




---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: new xml type

I suppose my original message wasn't that clear.  I'm not completely 
certain this idea is fully formed in my head either!  ;)

What I'm proposing is that the NAnt build script writer user would use 
the task outputs as if they were XML, but under the hood they would be 
fully-fledged C# classes.

We all agree that the "xml" object type that Martin is suggesting would 
be used within any XML task within the build script as raw XML.  It 
would fit snugly into the // tasks.

I'm proposing that we back these "xml" documents with fully-fledged C# 
objects in the NAnt backend.  I hope that this would lead to long-term, 
schema/class-enforced XML communication of some sort between tasks. 
Each task could expect and produce certain kinds of wellformed data.

Each "xml" input or output from an NAnt task would be mapped to an 
XmlSerializer-ready NAnt class, preferably backed by a true .xsd file 
somewhere within NAnt.  This serialization would be automatic and 
handled by the NAnt core without task writer intervention (modulo some 
attribute decoration).

If each xml object could tag along an associated schema, this would 
enforce the validity of the object during user manipulation of the XML 
object, allowing it to be "re-imported" into the NAnt world at some 
later date.

Does this make sense?

Scott Hernandez wrote:

This sounds interesting but I'm not sure I follow. Can you explain a little
more?
The concept of inputs/outputs to tasks (when called from other tasks) and
adding context info so tasks know about following task, and preceding tasks,
sounds interesting. But I'm not sure how this ties in here.
What would the user experience be? What would the syntax be?

- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>

For tasks (such as the solution task), what about having C# classes in
NAnt that map to XML itself?  They could appear as XML to
xmlpeek/xmlpoke/xmlforeach, but would be backed by C# classes internally.
This would make it far simpler to "return" values from tasks.

Martin Aliger wrote:


Hi all,

I'm trying to develop new xml type. Right now I have some preliminary
patch

to enable script like this:


 
  
   John
   Smith
  
  John Smith's life
 


 
 

How you like it? I'm looking forward to your comments...

What I want to do is something James and Ivan also proposed: add some
way to

return information from task back to script. I dont think that add
resultproperty/outputproperty to exec task and other whateverproperties
to

other tasks is good way. What I want to do is add one general attribute
(e.g. result) to all tasks. Result itself will be xml dom with
potentionaly

many values. exec task could for example have in it full commandline
executed, result code, stdout, stderr and maybe even more things! So it
could be written something like this:
   
   property="resultcode"/>

   
   
   
or even shorter when function for xmlpeek exists!

Martin




---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [Fwd: [Nprof-developers] Re: solution task]

 Original Message 
Subject: [Nprof-developers] Re: solution task
Date: Tue, 06 Jan 2004 11:09:22 -0700
From: Matthew Mastracci <[EMAIL PROTECTED]>
To: Martin Aliger <[EMAIL PROTECTED]>, 
[EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>

Sounds good to me too - just ensure that you've got compilerargs
specified by language.  There's a number of flags that are valid for a
single compiler only.
Martin Aliger wrote:

Hi all !

1/
Do you think, that now is good time to some cleaning and restructuring 
in solution task as we discussed earlier? I have some spare time and 
appetite to do that now!

2/
Also I would need (and like to) make some improvements to that task. 
What I need (and currently use not-commited patch) is need to custom 
arguments override like there:

We previously discuss that as it will be nice to do that at solution 
level or at project level. Do you still like the idea? I could implement 
that if you agree with that...

Regards,
Martin

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
Nprof-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nprof-developers

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: new xml type

For tasks (such as the solution task), what about having C# classes in 
NAnt that map to XML itself?  They could appear as XML to 
xmlpeek/xmlpoke/xmlforeach, but would be backed by C# classes internally.

This would make it far simpler to "return" values from tasks.

Martin Aliger wrote:

Hi all,

I'm trying to develop new xml type. Right now I have some preliminary patch
to enable script like this:
 
  
   
John
Smith
   
   John Smith's life
  
 

  
  

How you like it? I'm looking forward to your comments...

What I want to do is something James and Ivan also proposed: add some way to
return information from task back to script. I dont think that add
resultproperty/outputproperty to exec task and other whateverproperties to
other tasks is good way. What I want to do is add one general attribute
(e.g. result) to all tasks. Result itself will be xml dom with potentionaly
many values. exec task could for example have in it full commandline
executed, result code, stdout, stderr and maybe even more things! So it
could be written something like this:





or even shorter when function for xmlpeek exists!

Martin


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Basedir changes - possible problems

So it looks like the recent basedir changes have revealed a 
long-standing issue w.r.t. assumptions about the current directory.  It 
turns out that there are a few places where the tasks assume that the 
project's base directory is the same as the current directory.  The two 
big ones I've found are:

1.  The  element of the 
2.  The file loaded by 
I don't know where else in NAnt these problems might exist.  I've worked 
around it with this simple patch- should it be checked in?  The correct 
solution right now is to wrap all filename references with 
Project.GetFullPath(), but would it be better to just change our current 
directory to the project's base directory for the duration of the 
project run?

--- Project.cs  18 Dec 2003 18:22:33 -  1.61
+++ Project.cs  19 Dec 2003 22:06:37 -
@@ -784,8 +784,12 @@
 public bool Run() {
 Exception error = null;
 DateTime startTime = DateTime.Now;
+string oldDirectory = Directory.GetCurrentDirectory();
 try {
+// change to the base directory of the project before 
running anything
+Directory.SetCurrentDirectory(BaseDirectory);
+
 OnBuildStarted(this, new BuildEventArgs(this));
 Log(Level.Info, "Buildfile: {0}", BuildFileUri);

@@ -819,6 +823,9 @@
 // signal build failure
 return false;
 } finally {
+// restore the old directory
+Directory.SetCurrentDirectory(oldDirectory);
+
 string endTarget;
 if (error == null) {



Matt.

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] basedir changes

Well, with additional investigation, it appears that the problem is that 
something has broken the  element in my build file.

My build files are structured like so:

\build\scripts\nightly.build
basedir="."
\build\scripts\project1.build
basedir="../.."
It seems as if project1.build is ending up with the wrong current 
directory.

It may be related to this change (ianm, NAntTask.cs):

+try {
+// change current directory to directory of the build 
file that
+// will be run
+Directory.SetCurrentDirectory(Path.GetDirectoryName(
+Project.GetFullPath(BuildFileName)));
+// run the given build
+if (!project.Run()) {
+throw new BuildException("Nested build failed. 
Refer to build log for exact reason.");
+}
+} finally {

Can anyone confirm this?

This is my regression test investigation:

Nov 19. - works
Nov 27. - works
Nov 28. - works
(some checkin)
Dec 2. - failure
Dec 9. - failure
Matt.



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] basedir semantics change?

Has somebody modified the project basedir semantics?  The latest CVS 
version isn't working correctly for me.  It's acting as if the basedir 
attribute wasn't specified.

I'll try to find out the date that it was busted, but I'm curious if 
anyone remembers changing anything to do with this.

This is a CVS checkout+build from this morning.  Last working was my 
last checkout a few weeks ago.

Matt.

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Adding XML support to or new task

Scott Hernandez wrote:

This sounds interesting. Maybe we would want to introduce some
xpathselection elements to replace your property example. Properties in this
example would probably be a little confusing to the user since it isn't
really a regular property (the value is retrieved via xpath, not only via an
expression).
Agreed- it's much clearer in that case.  I think that 
xmlpeek/xmlpoke/xmlforeach would be a powerful combination.  Having an 
implicit XML context available to all three would also be great!







The  stuff could probably be cleaned up - it's certainly a 
"catch-all" for various types of iteration.  Perhaps we could split all 
the iteration tasks in some way.




etc...







...


It would be really cool if we make this work so that you could use the
 task to select from the open file (xmldocument). Then later when
if/when we get referencable types (for example an xml file factory or
something) we could just a little more efficient. It would be nice to use
the implied context here to simplify things.
;)

 could also be updated but this probably falls out of the scope
of that. This is pretty specialized, and will need to be very specific to
xml.
- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, December 18, 2003 12:25 PM
Subject: [nant-dev] Adding XML support to  or new task



I'm looking at adding XML iteration support for either the 
task or perhaps a new, yet-unnamed task.  I would like to be able to
iterate over a file based on an XPath query, picking up each matching
element or attribute in turn.   is the easiest place to add it,
but it's not really a clean solution.
A better way would be to model a new  task on the existing
xmlpeek/xmlpoke tasks like so:




${someattribute}, ${someinnertext}


How does this sound?




---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: Will there be a nAnt-0.84rc2 and final before the end of the year?

Gert - are we branched for 0.84?  I have some minor checkins I'm itching 
to get in for the 0.85.  I can also look at some solution cleanups over 
my vacation time in the next few weeks.

Gert Driesen wrote:

- Original Message - 
From: "Scott Hernandez" <[EMAIL PROTECTED]>
To: "Morris, Jason" <[EMAIL PROTECTED]>; "Nant-Developers (E-mail)"
<[EMAIL PROTECTED]>
Sent: Friday, December 19, 2003 1:14 AM
Subject: Re: [nant-dev] Will there be a nAnt-0.84rc2 and final before the
end of the year?

There will be a new RC in the next day or two (as I hear). The expression
stuff will not make this release.

I originally planned to release rc2 yesterday, but I was waiting on a more
detailed bug report from a user to check whether a fix for that particular
issue should be included in rc2, and I still haven't heard from him yet ...
There are also some reports about our  task not working on a .NET
1.0-only system that are disturbing me ...
I have to attend some festivities this weekend (read : drink lots of beer),
and probable won't be able to release it before monday (and even then, I
urgently have to do some christmas shopping, p) ... There's a slight
chance that I might be able to release it on saturday morning, but don't get
your hopes up ...

But it is now in the cvs HEAD, meaning that it is slated for the next
release. It still needs a lot of testing, but we hope to get a expression
feature complete version soon after the current release (.84).
Personally, I'd like to see a .85 release with expression support near the
first of the year!

I'll try to get NAnt 0.84 released by the end of next week, but a 0.85
release by the first of next year is not feasable I think ...
Gert

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Adding XML support to or new task

2003-12-18 Thread Matthew Mastracci

I'm looking at adding XML iteration support for either the  
task or perhaps a new, yet-unnamed task.  I would like to be able to 
iterate over a file based on an XPath query, picking up each matching 
element or attribute in turn.   is the easiest place to add it, 
but it's not really a clean solution.

A better way would be to model a new  task on the existing 
xmlpeek/xmlpoke tasks like so:





${someattribute}, ${someinnertext}


How does this sound?

Matt.



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: verbosity of some tasks

That's okay - I was mostly looking for the synchronization of 
dependent-file-parsing resource code between the two tasks.  I wasn't 
sure how much had been done already.

I agree with the license stuff- it's bizarre enough that it should be 
done by hand outside the  task.

Gert Driesen wrote:

An improved version of the resource code is actually already part of
CompilerBase, but it does not support licx files and I don't think it should
either ...
We should not change the compiler task into a mini-solution tasks

Gert

- Original Message ----- 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 7:48 PM
Subject: [nant-dev] Re: verbosity of some tasks



Sorry!  That was a think-o on my part.  I meant resource code.  Should
have read:
"It would be nice to move the *resource* code into a ... "

Been a tough week  ;)

Matt.

Gert Driesen wrote:


- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 7:27 PM
Subject: Re: verbosity of some tasks




That would be cool.  It would be nice to move the reference code into a
common place (the  and  tasks) to avoid code duplication.


Not sure if we need this for the compiler tasks, as you should actually
supply it with the assemblies that you want to reference ...
I don't think these tasks should contain any logic for determining other
dependencies, so there won't be any code duplication.
Gert




---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers






---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: verbosity of some tasks

Sorry!  That was a think-o on my part.  I meant resource code.  Should 
have read:

"It would be nice to move the *resource* code into a ... "

Been a tough week  ;)

Matt.

Gert Driesen wrote:

- Original Message - 
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 7:27 PM
Subject: Re: verbosity of some tasks



That would be cool.  It would be nice to move the reference code into a
common place (the  and  tasks) to avoid code duplication.


Not sure if we need this for the compiler tasks, as you should actually
supply it with the assemblies that you want to reference ...
I don't think these tasks should contain any logic for determining other
dependencies, so there won't be any code duplication.
Gert




---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Re: verbosity of some tasks

That would be cool.  It would be nice to move the reference code into a 
common place (the  and  tasks) to avoid code duplication.

Matt.

Gert Driesen wrote:

- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, December 03, 2003 9:44 PM
Subject: [nant-dev] Re: verbosity of some tasks

At some point I'd like to use the multiple .resx input of resgen.exe -
it would be nice to swallow output if no errors occur and just output:
[resgen] Transformed 5 .resx files

The solution builds would be a lot easier to read.  Perhaps I can
compress all of the reference copy operations into a single task call as
well.

After the 0.84 release, we should focus some of our efforts on refactoring
the solution task and have it use the compiler tasks instead...
It would be great if you could participate in this effort, as you're the
original author ...
Gert

---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Re: project references problems in task