Re: [nant-dev] Fwd: Solution MsBuild support for .net 4.0

2010-06-09 Thread Gert Driesen
Hey Gert,

 

Sorry about that, but in this age of spam moderating lists has become a
full-time job.

We cannot make a distinction between spam and posts from list members that
need to be approved, so we'd have to inspect each message individually.

This is not something any of us has enough timeslots for.

 

Hope you understand,

 

Gert

 

From: Gert Kello [mailto:gert.ke...@mail.ee] 
Sent: woensdag 9 juni 2010 6:30
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Fwd: Solution MsBuild support for .net 4.0

 

Hmm, seems like the list moderators are not very active... First mail went
over 40kB, but so far it did not get approved by moderator.

So here they go in zipped format.

Gert

-- Forwarded message --
From: Gert Kello gert.ke...@mail.ee
Date: 7 June 2010 15:21
Subject: Solution MsBuild support for .net 4.0
To: nant-developers@lists.sourceforge.net


Hi.

Here are three patches to improve solution task support for MsBuild:

1. MultiNetMsBuild.patch - builds three different assemblies to support
MsBuild, for .net 2.0, 3.5 and 4.0. Mono support is missing/not tested for
3.4 and 4.0. Well not sure if the conditional build structure I used is
considered to be Ok (in src/NAnt.MSBuild/NAnt.MSBuild.build)
2. BetterVsNetSystemAssemblyPathResolve.patch - use
TargetFramework.ResolveAssembly() instead of
TargetFramework.FrameworkAssemblyDirectory when resolving solution task
project references
3. BetterRefPathresolveForFixing.patch - improved search for build
dependencies inside solution task. I proposed that patch a long time ago,
but seems like not included.
(http://www.mail-archive.com/nant-us...@lists.sourceforge.net/msg09925.html)

Gert 

 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2924 - Release Date: 06/07/10
20:35:00

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Announcing NAnt 0.91 Alpha1

2010-05-31 Thread Gert Driesen
Hey Martin,

I added the missing file to NAnt.Win32.csproj.
I don't immediately see an advantage to converting our project file as long
as VS supports converting them to the version you're using.

Thanks,

Gert

-Original Message-
From: Martin Aliger [mailto:martin_ali...@gordic.cz] 
Sent: maandag 31 mei 2010 17:44
To: 'Ryan Boggs'; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Announcing NAnt 0.91 Alpha1

Ryan,

Please add LocateSdkTask.cs into NAnt.Win32.csproj. 

Maybe it will save someones hour of life. It took an hour to me right now
wondering, why I cant even run nant -t:net-4.0 :-)


As side note:
All csprojs are now VS2003 projects. I dont even have this anymore. Should
we convert those to some of newer (2005,2008,2010) ?



Ing. Martin Aliger
martin_ali...@gordic.cz



-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: Sunday, May 30, 2010 4:03 AM
To: mono-l...@lists.ximian.com; nant-us...@lists.sourceforge.net;
nant-developers@lists.sourceforge.net; nant-annou...@lists.sourceforge.net
Subject: [nant-dev] Announcing NAnt 0.91 Alpha1

Announcing NAnt 0.91 Alpha1
We are proud to announce the first alpha release of NAnt 0.91, the
first official release with .NET 4.0 support.

The primary goal for this release is to improve support for .NET 4.0.
Please give this release a test and report any NAnt core specific bugs
back along with examples as soon as you can.

This release focuses on extending our already strong support for
multiple target frameworks, bringing improved flexibility and
performance.  A number of outstanding issues have been fixed as well.

A roadmap has been created to help illustrate the current release
plan.  Please note that this roadmap is a work in progress and is
subject to change depending on feature priorities, issues, and
developer's comfort level with the release:
https://sourceforge.net/apps/mediawiki/nant/index.php?title=Roadmap

Binary and source distributions are available for immediate download from:
http://sourceforge.net/project/showfiles.php?group_id=31650

The CVS tag for NAnt 0.91Alpha1 is:
rel-0-91-alpha1

Instruction for checking out sources from CVS are available here:
http://sourceforge.net/cvs/?group_id=31650

Discussion of NAnt occurs on the mailing list at
nant-us...@lists.sourceforge.net.

Bugs can be reported using the Bug Tracker at
http://sourceforge.net/projects/nant.

For more detailed progress on the inner workings of NAnt, check out
the NAnt Blog at https://sourceforge.net/apps/wordpress/nant/

About NAnt:
NAnt is a free .NET build tool, allowing applications to be built
targeting both Microsoft .NET and Mono while supporting both Windows
and Linux platforms.

Check the NAnt homepage for additional info at http://nant.sourceforge.net.

Thanks,
Ryan


--

___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers



--

___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.819 / Virus Database: 271.1.1/2907 - Release Date: 05/30/10
20:25:00


--

___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1

2010-04-18 Thread Gert Driesen
Ryan,

The Mono team is dropping support for .NET Framework 1.x, hence mcs is no
longer available.
I believe Mono 2.6.x is the last release to support .NET 1.x.

We'll just need to check what version of Mono is available, or just check
for the compiler that is available (1.x: mcs, 2.x: gmcs, 4.x: dmcs).
Good thing NAnt build authors to not have to deal with this.

Martin, please submit a bug report for this.

Gert

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: zondag 18 april 2010 3:27
To: Martin Gainty
Cc: nant-developers@lists.sourceforge.net;
nant-annou...@lists.sourceforge.net; nant-us...@lists.sourceforge.net
Subject: Re: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1

Hey Martin,

What Linux are you running?

Thanks,
Ryan

On Sat, Apr 17, 2010 at 6:16 PM, Martin Gainty mgai...@hotmail.com wrote:
 Hi Ryan

 any suggestion as to where i can obtain mcs?

 $ make
 mkdir -p bootstrap
 cp -R lib/ bootstrap/lib
 # Mono loads log4net before privatebinpath is set-up, so we need this in
the
 sam
 e directory
 # as NAnt.exe
 cp lib/common/neutral/log4net.dll bootstrap
 cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config
 mcs -target:exe -define:MONO -out:bootstrap\\NAnt.exe
 -r:bootstrap\\log4net.dll
 \
     -recurse:src\\NAnt.Console\\*.cs
src\\CommonAssemblyInfo.cs
 /bin/sh: mcs: command not found

 ?
 Thanks!
 Martin Gainty
 __
 Note de déni et de confidentialité

 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
 destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
copie
 de ceci est interdite. Ce message sert à l'information seulement et n'aura
 pas n'importe quel effet légalement obligatoire. Étant donné que les email
 peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
 aucune responsabilité pour le contenu fourni.




 Date: Sat, 17 Apr 2010 17:34:49 -0700
 From: rmbo...@gmail.com
 To: nant-developers@lists.sourceforge.net;
 nant-us...@lists.sourceforge.net; nant-annou...@lists.sourceforge.net
 Subject: [NAnt-users] Announcing NAnt 0.90-beta1

 Announcing NAnt 0.90-beta1

 The first beta of NAnt 0.90 has been released. Please continue to
 test and report bugs so we can make the final release of 0.90 the best
 it can be.

 A roadmap has been created to help illustrate the current release
 plan. Please note that this roadmap is a work in progress and is
 subject to change depending on feature priorities, issues, and
 developer's comfort level with the release:
 https://sourceforge.net/apps/mediawiki/nant/index.php?title=Roadmap

 This release focuses on extending our already strong support for
 multiple target frameworks, bringing improved flexibility and
 performance. A number of outstanding issues have been fixed as well.

 Binary and source distributions are available for immediate download
from:
 http://sourceforge.net/project/showfiles.php?group_id=31650

 The CVS tag for NAnt 0.90 Beta1 is:
 rel-0-90-beta1

 Instruction for checking out sources from CVS are available here:
 http://sourceforge.net/cvs/?group_id=31650

 Discussion of NAnt occurs on the mailing list at
 nant-us...@lists.sourceforge.net.

 Bugs can be reported using the Bug Tracker at
 http://sourceforge.net/projects/nant.

 About NAnt:
 NAnt is a free .NET build tool, allowing applications to be built
 targeting both Microsoft .NET and Mono while supporting both Windows
 and Linux platforms.

 Check the NAnt homepage for additional info at
 http://nant.sourceforge.net.

 Thanks,
 Ryan




--
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 NAnt-users mailing list
 nant-us...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-users

 
 Hotmail has tools for the New Busy. Search, chat and e-mail from your
inbox.
 Learn more.


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2815 - Release Date: 04/16/10
20:31:00



Re: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1

2010-04-18 Thread Gert Driesen
Hey Ryan,

Thanks for getting to the bottom of this.
Regardless of whether this'll fix the problem for Martin, we need to improve
our makefile to support other (mono) compilers beside mcs.
Can you add this to our roadmap ?

Thanks!

Gert

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: zondag 18 april 2010 22:14
To: Martin Gainty
Cc: gert.drie...@telenet.be; nant-developers@lists.sourceforge.net;
nant-annou...@lists.sourceforge.net; nant-us...@lists.sourceforge.net
Subject: Re: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1

Hey Martin,

Before going through the trouble of opening up a bug report, could you
try the following command(s) please?  Forgive me but since I don't
know what Linux you are running, I am just going to list the most
common ones.

OpenSUSE:
(sudo) zypper install mono-complete

Ubuntu:
(sudo) aptitude install mono-complete

More details can be found in the NAnt Wiki:
http://sourceforge.net/apps/mediawiki/nant/index.php?title=Development_Guide

In case anyone is wondering, the main cause of this kind of error on a
Linux system is that the distro you are running has separated the mono
essentials from the mono compilers to reduce installation overhead
(because you usually don't need the compilers to run precompiled
applications on mono).  Usually installing a Mono-devel type package
will resolve this but mono-complete will get everything in one shot
without the guess work.  Just make sure you don't depend your
package(s) on the mono-complete package.

If installing mono-complete doesn't fix this issue, then you should
open a bug report over at sourceforge.net.

Thanks,
Ryan

On Sun, Apr 18, 2010 at 12:50 PM, Martin Gainty mgai...@hotmail.com wrote:
 will do gert..could you provide a link where i can submit this bug?

 bedankt,
 Martin
 __
 Jogi és Bizalmassági kinyilatkoztatás/Verzicht und
 Vertraulichkeitanmerkung/Note de déni et de confidentialité

 Ez az üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük,
hogy
 jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
készítése
 nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és semmiféle
jogi
 alkalmazhatósága sincs.  Mivel az electronikus üzenetek könnyen
 megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet
 tartalma miatt.

 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
 Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
 Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
 dient lediglich dem Austausch von Informationen und entfaltet keine
 rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
 E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
 destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
copie
 de ceci est interdite. Ce message sert à l'information seulement et n'aura
 pas n'importe quel effet légalement obligatoire. Étant donné que les email
 peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
 aucune responsabilité pour le contenu fourni.




 From: gert.drie...@telenet.be
 To: rmbo...@gmail.com; mgai...@hotmail.com
 CC: nant-developers@lists.sourceforge.net;
 nant-annou...@lists.sourceforge.net; nant-us...@lists.sourceforge.net
 Subject: RE: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1
 Date: Sun, 18 Apr 2010 09:28:40 +0200

 Ryan,

 The Mono team is dropping support for .NET Framework 1.x, hence mcs is no
 longer available.
 I believe Mono 2.6.x is the last release to support .NET 1.x.

 We'll just need to check what version of Mono is available, or just check
 for the compiler that is available (1.x: mcs, 2.x: gmcs, 4.x: dmcs).
 Good thing NAnt build authors to not have to deal with this.

 Martin, please submit a bug report for this.

 Gert

 -Original Message-
 From: Ryan Boggs [mailto:rmbo...@gmail.com]
 Sent: zondag 18 april 2010 3:27
 To: Martin Gainty
 Cc: nant-developers@lists.sourceforge.net;
 nant-annou...@lists.sourceforge.net; nant-us...@lists.sourceforge.net
 Subject: Re: [nant-dev] [NAnt-users] Announcing NAnt 0.90-beta1

 Hey Martin,

 What Linux are you running?

 Thanks,
 Ryan

 On Sat, Apr 17, 2010 at 6:16 PM, Martin Gainty mgai...@hotmail.com
 wrote:
  Hi Ryan
 
  any suggestion as to where i can obtain mcs?
 
  $ make
  mkdir -p bootstrap
  cp -R lib/ bootstrap/lib
  # Mono loads log4net before privatebinpath is set-up, so we need this
in
 the
  sam
  e directory
  # as NAnt.exe
  cp lib/common/neutral/log4net.dll bootstrap
  cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config
  mcs -target:exe -define:MONO -out:bootstrap\\NAnt.exe
  -r:bootstrap\\log4net.dll
  \
      -recurse:src\\NAnt.Console\\*.cs
 src\\CommonAssemblyInfo.cs
  /bin/sh: mcs: command not 

Re: [nant-dev] Bug tracker tag for 0.9

2010-04-03 Thread Gert Driesen
Hey Charles,

 

I now added 0.90-alpha1 as version to the bug tracker.

Regarding the error users get when clicking the nodes directly under
releases (eg. 0.90-alpha1):  we can either enable directory browsing, or we
can remove these links (or just expand the node when clicked). I think the
latter is more appropriate, as all files are available as child nodes.

 

Gert

 

From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: donderdag 1 april 2010 22:24
To: Richard Birkby; Gert Driesen
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Bug tracker tag for 0.9

 


Hello Richard,

Thanks for trying it and the feedback.

1) Gert, can you help add the version please? (I don't have the necessary
permissions to add the version to the bug tracker.)

2) In terms of the console bug, I have seen it as well. I mentioned it a
while back, but no one has the answer. It is definitely something I plan to
fix for 0.90 RTM. (My suspicion is that it was introduced in between 0.85
and 0.86-beta1). Please enter a ticket once the version has been added to
the bug tracker. 

3) I think SF has changed the location of the files since 2 years ago. This
is a simple fix.

Thanks,
Charles

--- On Thu, 4/1/10, Richard Birkby rbir...@gmail.com wrote:


From: Richard Birkby rbir...@gmail.com
Subject: [nant-dev] Bug tracker tag for 0.9
To: nant-developers@lists.sourceforge.net
Received: Thursday, April 1, 2010, 8:06 PM

Congrats on releasing 0.9a1.

 

I immediately put it into our build process and found an issue -
unfortunately, I can't enter the issue into Nant's bug tracker because a
0.9a1 tag is missing - any chance you could add one?

 

I also noticed if I click on Releases-0.90 Alpha 1 in the left hand
navigation bar on the Nant homepage, it takes me to the following page which
gives an error:
http://nant.sourceforge.net/release/0.90-alpha1/

 

The bug which I was unable to enter is that when I use Nant-Contrib's
MSBuild task, all output from the task is concatenated onto a single line
with no carriage returns.

 

 

Thanks

Richard

 

  _  

  http://us.i1.yimg.com/us.yimg.com/i/ca/iotg_search.jpg
http://ca.toolbar.yahoo.com/ Yahoo! Canada Toolbar : Search from anywhere
on the web and bookmark your favourite sites. Download it now! 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2782 - Release Date: 04/01/10
20:32:00

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] sysinfo task

2010-03-26 Thread Gert Driesen
Hey Ryan,

Check the docs of the sysinfo task.
Note that its not officially deprecated, so I'd still fix any issues.

Gert

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: vrijdag 26 maart 2010 15:53
To: Dominik Guder
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] sysinfo task

Hi,

On Mar 26, 2010, at 2:07 AM, Dominik Guder o...@guder.org wrote:

 Am 25.03.2010 17:12, schrieb Gert Driesen:
 Hi Ryan,

 I guess it won't make it in time for the 0.90 release.
 Personally, I even consider the sysinfo task deprecated.


 On Mar 25, 2010, at 8:10 AM, Gert Driesen gert.drie...@telenet.be 
 
 wrote:

 Ryan,

 We cannot allow parenthesis in property names, as that would  
 screw
 up our expression tokenizer.
 I'm more enclined to a machanism that allows explicit control  
 over
 the property names that a given environment variable is mapped  
 to.
 Something similar to the file mappers in Ant would be great.

 If I understand you correctly, are you referring to something  
 like:

 sysinfo
 mapper type=glob from=*(* to=*_* /
 /sysinfo

 Am I understanding you right?


 Hi,

 sorry, I did not write that I checked the parens handling in
 properties and found out that the parser will fail. The mapper  
 solution
 looks good but as Gert stated sysinfo is kind of deprecated. So we
 might not put to much effort into it.

Does anyone know if sysinfo was replaced by anything?  This would be  
good to know.

 Another point which needs attantion (propably for 1.0) is that I was
 able to define a property with parens without getting an exception at
 definition time. More detail later.

Can you provide an example when you get a moment? I would like to look  
into this.

 First of all I want to get these tests green for 0.90 release.
 My proposal:
 - add failonerror='true' to all existing tests
 - add a new test which throws BuildException for
 Environment.ProgramFiles(64)
 - fix docu
 - sort output

 What do you think?

I like it.

 Regards Dominik

 -- 
 The answer to the great question of life,
 the universe and everything is 42 (Douglas Adams)

 --- 
 --- 
 --- 
 -
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

Thanks,
Ryan


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2769 - Release Date: 03/25/10
21:50:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] sysinfo task

2010-03-25 Thread Gert Driesen
Ryan,

We cannot allow parenthesis in property names, as that would screw up our 
expression tokenizer.
I'm more enclined to a machanism that allows explicit control over the 
property names that a given environment variable is mapped to.
Something similar to the file mappers in Ant would be great.

Gert

--
From: Ryan Boggs rmbo...@gmail.com
Sent: Thursday, March 25, 2010 3:59 PM
To: Dominik Guder o...@guder.org
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] sysinfo task

 Hi,

 On Mar 25, 2010, at 3:34 AM, Dominik Guder o...@guder.org wrote:


 On 64bit systems there are some environment variables which contains
 parentheses like *ProgramFiles(x86)* or *CommonProgramFiles(x86)*.
 This are invalid property names which cause the sysinfo tasks to
 fail.

 b) replace any parentheses in env.name with underscores and put this
 into docu.

 So I would like to go with b) since the properties could be used.
 In addition docu states that function *environment::get-variable()*
 should be used to retrieve env variables. So I think this won't
 affect a
 lot of users.


 Ok, I did some checks and will add some patches for discussion.
 (text in [[[ ]]] might be used for commit message as seen at svn
 mailing list)

 [[[
 fix incorrect definition of failonerror in sysinfo docu.
 ]]]
 sysinfo-task-docu-error.patch


 sysinfo-replace-propname.patch:
 this is a first implementation to replace sys.env.ProgramFiles
 (x86) with sys.env.ProgramFiles_x86_
 There is still the docu change missing. But I will provide this when
 we are going this way.

 Are we sure that we want to alter env var names like this?  Wouldn't
 it be better to allow parenthesis in the var names? I can just see
 this causing confusion when a user is looking for an altered var name.

 Result:
 --- snip ---
  [sysinfo] sys.env.ProgramFiles = C:\Programme
  [sysinfo] sys.env.ProgramFiles_x86_ = C:\Programme
 --- snap ---


 [[[
 sort sysinfo properties when using verbose=true
 ]]]
 sysinfo-verbose-sorted.patch:

 This patch will output properties on sorted order in verbose. I
 found that I need to search more than I like to find my replaced
 property without this sorting

 This makes sense to me.

 So far Dominik

 -- 
 The answer to the great question of life,
 the universe and everything is 42 (Douglas Adams)
 sysinfo-task-docu-error.patch
 sysinfo-replace-propname.patch
 sysinfo-verbose-sorted.patch
 --- 
 --- 
 --- 
 -
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 Thanks,
 Ryan

 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt License

2010-03-20 Thread Gert Driesen
Hey Ryan,

Correct. There were plans once to change this, but it never happened (I'm
afraid).

Gert

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: dinsdag 16 maart 2010 2:53
To: gert.drie...@telenet.be; nant-developers@lists.sourceforge.net
Subject: NAnt License

Hi,

I just want to confirm that NAnt is currently licensed under the
GPLv2.  It's not dual licensed with GPLv2 and LGPL or anything like
that, correct?

Thanks,
Ryan

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2747 - Release Date: 03/15/10
20:33:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt License

2010-03-20 Thread Gert Driesen
Ryan,

Problem is that you need consent from everyone that contributed code.
Note that I definitely don't have a problem with a more liberal license.

Gert

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: zaterdag 20 maart 2010 17:46
To: Gert Driesen
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] NAnt License

Het Gert,

On Mar 20, 2010, at 1:15 AM, Gert Driesen gert.drie...@telenet.be  
wrote:

 Hey Ryan,

 Correct. There were plans once to change this, but it never happened  
 (I'm
 afraid).

Yeah, I saw that plan in an old roadmap awhile ago. Is there a  
possibility that it could change in the future or is that just not  
possible at this point?

Thanks,
Ryan

 Gert

 -Original Message-
 From: Ryan Boggs [mailto:rmbo...@gmail.com]
 Sent: dinsdag 16 maart 2010 2:53
 To: gert.drie...@telenet.be; nant-developers@lists.sourceforge.net
 Subject: NAnt License

 Hi,

 I just want to confirm that NAnt is currently licensed under the
 GPLv2.  It's not dual licensed with GPLv2 and LGPL or anything like
 that, correct?

 Thanks,
 Ryan

 No virus found in this incoming message.
 Checked by AVG - www.avg.com
 Version: 9.0.733 / Virus Database: 271.1.1/2747 - Release Date:  
 03/15/10
 20:33:00



--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2756 - Release Date: 03/19/10
08:33:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Problem running NAnt tests.

2010-03-10 Thread Gert Driesen
Hey Charles,

Are you running the tests using the test target, or using the NUnit GUI ?
It's been a while since I ran the tests, but last time they were just fine.
Can you send me an example of this mal-formatted output ?

Gert

--
From: Charles Chan cchan...@users.sourceforge.net
Sent: Wednesday, March 10, 2010 6:24 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Problem running NAnt tests.

 Hello,

 I have been trying to run the tests in the past few days, and I see the 
 output is mal-formatted. The line breaks are not there and it's hard to 
 see which tests are failing (or the stacktrace).

 Can anyone confirm if they are seeing the following when they run the 
 tests?
 1) formatting problem
 2) some failing tests

 Just want to make sure it's not a simple mistake on my part.

 Regards,
 Charles



  __
 The new Internet Explorer® 8 - Faster, safer, easier.  Optimized for 
 Yahoo!  Get it Now for Free! at 
 http://downloads.yahoo.com/ca/internetexplorer/

 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] DocManager pages are now merged into MediaWiki

2010-03-05 Thread Gert Driesen
Thanks dude!

-Original Message-
From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: zaterdag 6 maart 2010 4:25
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] DocManager pages are now merged into MediaWiki

Big thanks to SF OPS -- the (old) documents have now been migrated into NAnt
MediaWiki!

Currently, these (old) pages are not listed under the main page. 
Instead you can find them under:
https://sourceforge.net/apps/mediawiki/nant/index.php?title=Old_Docmanager_I
ndex

Please feel free to take a look. The contents will be updated and/or
incorporated into the main Wiki in the next little while.

Besides being a developer, there are lots of different way to contribute to
the project. If anyone wishes to help with the documentation updates (or any
other aspects of the project for that matter), please let me know. 

Regards,
Charles


  __
Make your browsing faster, safer, and easier with the new Internet ExplorerR
8. Optimized for Yahoo! Get it Now for Free! at
http://downloads.yahoo.com/ca/internetexplorer/


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2725 - Release Date: 03/05/10
20:34:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Task/planning for 0.87 release

2010-03-05 Thread Gert Driesen
Hi Ryan,

That would be great.
We could also look for an alternative in parallel (as NDoc is no longer
maintained).

Gert

-Original Message-
From: Ryan Boggs [mailto:rmboggs.obsd.po...@gmail.com] 
Sent: zaterdag 6 maart 2010 2:09
To: Gert Driesen
Cc: nant-developers@lists.sourceforge.net; cchan...@users.sourceforge.net
Subject: Re: [nant-dev] Task/planning for 0.87 release

Hi,

On Thu, Mar 4, 2010 at 9:49 PM, Gert Driesen gert.drie...@telenet.be
wrote:
 Hi Charles,

 The docs clearly state that the dependent targets are always executed
 (first):

 Note: the dependencies of a target are always executed before testing the
 target's condition.
 Source:
 http://nant.sourceforge.net/release/latest/help/fundamentals/targets.html

 This makes sense, you actually may want to use the dependent targets to
set
 a property which controls whether the conditional target is executed.

 target name=clean-registry depends=determine-platform-capabilities
 if=${platform.supports.registry}
        ...
 /target

 In case of the NAnt build file: the proper way to deal with this is to fix
 the performance issue on Mono.
 But I'm afraid that'll take some time (find the problem, fix it, and then
 wait for the fix to be included in a release).


Ok, if no one minds, I would like to look into this further.

 Regards,

 Gert

 -Original Message-
 From: Charles Chan [mailto:cchan...@users.sourceforge.net]
 Sent: vrijdag 5 maart 2010 4:26
 To: Ryan Boggs
 Cc: Gert Driesen; nant-developers@lists.sourceforge.net
 Subject: Re: [nant-dev] Task/planning for 0.87 release

 Hello Ryan,

 Thanks for looking into this. Yeah I follow what you are saying (but I
 couldn't really test it ... see my other post.)

 The question basically comes down to this: If the target has a conditional
 expression. What order is it evaluated in? (I checked the NAnt doc. but it
 did not specify this clearly.)

 eg.
    target name=install-windows depends=userdoc
 if=${platform::is-win32()}

 Base on your comments, right now, the depends target is executed BEFORE
the
 condition is tested on a Linux system.

 Logically, however, if the condition expression is false, then the current
 target is not going to be executed, and in this case, neither should the
 depends target.

 So ... to ensure .build scrips are executed as efficiently as possible,
 yeah, I agree in this case it probably *should* be fixed. ie. only execute
 the depends and target IFF if/unless attribute tests is true.

 On the other hand, since I don't know the history behind this, I would
like
 to listen to what the senior developers have to say first. This behavior
 might be used in production and my concern is that changing it now might
 affect these users during an upgrade -- even if it was a bug in the
 software.

 Regards,
 Charles

 --- On Fri, 3/5/10, Ryan Boggs rmboggs.obsd.po...@gmail.com wrote:

 From: Ryan Boggs rmboggs.obsd.po...@gmail.com
 Subject: Re: [nant-dev] Task/planning for 0.87 release
 To: cchan...@users.sourceforge.net cchan...@users.sourceforge.net
 Cc: Gert Driesen gert.drie...@telenet.be,
 nant-developers@lists.sourceforge.net
 nant-developers@lists.sourceforge.net
 Received: Friday, March 5, 2010, 1:35 AM
 Hi,

 Me again.  I noticed something in the current
 NAnt.build file that may
 be causing the massive *nix delay, or at least making it
 worse.  The
 install target on line 822, which I believe is being called
 by
 (n)make, lists two depending targets called install-windows
 and
 install-linux.  Looking at these targets, only the
 install-windows
 depends on the userdoc target which takes 30 minutes to run
 on
 Mono/*nix.  The install-linux target only depends on
 the build target.
  As a test, I removed the install-windows target from the
 install
 target depends list and reran on Linux.  NAnt was
 installed in less
 than 5 minutes.  This makes me think that NAnt is
 building the target
 depends before it is checking the target's if
 statement.  If that is
 true, is this functionality intended?  I would think
 that the if
 statement would need to be checked prior to running the
 depended
 targets.

 Hope this makes sense.

 Thanks,
 Ryan



      __
 Looking for the perfect gift? Give the gift of Flickr!

 http://www.flickr.com/gift/

 No virus found in this incoming message.
 Checked by AVG - www.avg.com
 Version: 9.0.733 / Virus Database: 271.1.1/2722 - Release Date: 03/04/10
 20:34:00





-- 
Thanks,
Ryan


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net

Re: [nant-dev] Task/planning for 0.87 release

2010-03-04 Thread Gert Driesen
Hi Charles,

The docs clearly state that the dependent targets are always executed
(first):

Note: the dependencies of a target are always executed before testing the
target's condition.
Source:
http://nant.sourceforge.net/release/latest/help/fundamentals/targets.html

This makes sense, you actually may want to use the dependent targets to set
a property which controls whether the conditional target is executed.

target name=clean-registry depends=determine-platform-capabilities
if=${platform.supports.registry}
...
/target

In case of the NAnt build file: the proper way to deal with this is to fix
the performance issue on Mono.
But I'm afraid that'll take some time (find the problem, fix it, and then
wait for the fix to be included in a release).

Regards,

Gert

-Original Message-
From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: vrijdag 5 maart 2010 4:26
To: Ryan Boggs
Cc: Gert Driesen; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Task/planning for 0.87 release

Hello Ryan,

Thanks for looking into this. Yeah I follow what you are saying (but I
couldn't really test it ... see my other post.)

The question basically comes down to this: If the target has a conditional
expression. What order is it evaluated in? (I checked the NAnt doc. but it
did not specify this clearly.)

eg.
target name=install-windows depends=userdoc
if=${platform::is-win32()}

Base on your comments, right now, the depends target is executed BEFORE the
condition is tested on a Linux system.

Logically, however, if the condition expression is false, then the current
target is not going to be executed, and in this case, neither should the
depends target.

So ... to ensure .build scrips are executed as efficiently as possible,
yeah, I agree in this case it probably *should* be fixed. ie. only execute
the depends and target IFF if/unless attribute tests is true.

On the other hand, since I don't know the history behind this, I would like
to listen to what the senior developers have to say first. This behavior
might be used in production and my concern is that changing it now might
affect these users during an upgrade -- even if it was a bug in the
software.

Regards,
Charles

--- On Fri, 3/5/10, Ryan Boggs rmboggs.obsd.po...@gmail.com wrote:

 From: Ryan Boggs rmboggs.obsd.po...@gmail.com
 Subject: Re: [nant-dev] Task/planning for 0.87 release
 To: cchan...@users.sourceforge.net cchan...@users.sourceforge.net
 Cc: Gert Driesen gert.drie...@telenet.be,
nant-developers@lists.sourceforge.net
nant-developers@lists.sourceforge.net
 Received: Friday, March 5, 2010, 1:35 AM
 Hi,
 
 Me again.  I noticed something in the current
 NAnt.build file that may
 be causing the massive *nix delay, or at least making it
 worse.  The
 install target on line 822, which I believe is being called
 by
 (n)make, lists two depending targets called install-windows
 and
 install-linux.  Looking at these targets, only the
 install-windows
 depends on the userdoc target which takes 30 minutes to run
 on
 Mono/*nix.  The install-linux target only depends on
 the build target.
  As a test, I removed the install-windows target from the
 install
 target depends list and reran on Linux.  NAnt was
 installed in less
 than 5 minutes.  This makes me think that NAnt is
 building the target
 depends before it is checking the target's if
 statement.  If that is
 true, is this functionality intended?  I would think
 that the if
 statement would need to be checked prior to running the
 depended
 targets.
 
 Hope this makes sense.
 
 Thanks,
 Ryan



  __
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2722 - Release Date: 03/04/10
20:34:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Task/planning for 0.87 release

2010-03-03 Thread Gert Driesen
Hey Charles,

AFAIK this is a Mono issue. I get the same bad performance on Mono/Windows.
However, I'm sure our implementation can be optimized a lot.

Gert

-Original Message-
From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: donderdag 4 maart 2010 6:42
To: Ryan Boggs
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Task/planning for 0.87 release

Hello Ryan,

I don't know, but something doesn't sound right. Thanks for pointing it out.

I have provided Dominik with access to TC, and I believe he is going to try
setup the Windows build. Since I didn't receive any offers for Linux, I
guess I will investigate this myself in parallel. This needs to be looked at
for 0.87 release anyways.

Regards,
Charles

--- On Thu, 3/4/10, Ryan Boggs rmboggs.obsd.po...@gmail.com wrote:

 From: Ryan Boggs rmboggs.obsd.po...@gmail.com
 Subject: Re: [nant-dev] Task/planning for 0.87 release
 To: cchan...@users.sourceforge.net
 Cc: nant-developers@lists.sourceforge.net
 Received: Thursday, March 4, 2010, 5:11 AM
 Yeah, but this brings up another
 issue I've noticed on both Linux and Mac..
 
 It took 1689.9 seconds to build on my Debian box. 
 1675.7 seconds were
 spent on that userdoc section.
 
 What is going on in that userdoc section and why does it
 take so long
 on non-win32 systems?


  __
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2719 - Release Date: 03/03/10
20:34:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Drop support for .NET-1.x?

2010-02-25 Thread Gert Driesen
Hey Charles,

You should make it clear if you want to drop sypport for .NET 1.x as a 
runtime environment (CLR), or as a target framework.

Regards,

Gert

--
From: Charles Chan cchan...@users.sourceforge.net
Sent: Thursday, February 25, 2010 4:20 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Drop support for .NET-1.x?

 Hello,

 Looking at the current state, I think it's too difficult to maintain 
 support for all of the .NET frameworks. Can we drop support for .NET 1.x 
 and beginning beginning .NET 2.0 as a minimum? If there are no objections, 
 I am going to change the default release from 
 set-net-1.0-framework-configuration to 
 set-net-2.0-framework-configuration

 Also, I want to enlist the help of more developers to get more work done, 
 faster.
 I think SF has a way of advertising for help, where is it?

 Regards,
 Charles



  __
 Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
 favourite sites. Download it now
 http://ca.toolbar.yahoo.com.

 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Drop support for .NET-1.x?

2010-02-25 Thread Gert Driesen
Hey Charles,

I have no problem with dropping .NET 1.x as supported runtime, but I
definitely want to retain .NET 1.x as target framework.
There's no reason why we should drop support for that.

Regards,
Gert

-Original Message-
From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: vrijdag 26 februari 2010 4:39
To: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Drop support for .NET-1.x?

Thanks for all of your replies! Sorry, I am a little busy today, so please
excuse me for the quick answers.

Gert:
Based on my understanding: (please correct if I am wrong)
Requires .NET-1.0 SDK / VS2002 to target .NET-1.0 -- The SDK is no longer
available from MS, making it difficult to develop or provide further support
for NAnt?
Requires .NET-1.1 SDK / VS2003 to target .NET-1.1
Requires .NET 2.0 SDK / VS2005 to target .NET 2.0

So I am hoping to drop support for .NET 1.x (at least .NET 1.0) runtime AND
target ASAP.


Ryan, Matt:
Your comments makes sense. FYI, I am planning to first release a new version
0.87-beta, rc, etc. (it's been too long since 0.86 and many changes since,
so I want to use a new number to signify the differences) This is mainly a
bugfix release. No new feature, but mainly to work towards a golden 1.0
version of NAnt to complete the 0.8x roadmap. 

Roadmap
===
0.87 - bug fix only to stabilize the existing features; eg. Mono/.NET
compatibilities issues.

1.00 - golden release, perhaps last version to support .NET 1.0
2.00 - add support for .NET 2.0, 3.5; VS solution 2005, 2008; update NUnit,
etc.

Thoughts? 
(Once we all reach a consensus, we can work on further breakdowns, divide up
the work, scan the bug lists, etc).


All:
Thanks very much for you interest, unfortunately, I only have developer
privilege so perhaps one of the project admins can help setup the
permissions. (Gert? Gerry? Can you help?) 

I am interested in learning more about your backgrounds and why you are
interested in helping NAnt. I assume most of you are using NAnt in the
workplace? How much time can you spend on this project? Is there any aspect
you are particularly interested in working in? 

If you know anyone who might be interested in contributing, please help
spread the word! 

Cheers,
Charles


  __
Connect with friends from any web browser - no download required. Try the
new Yahoo! Canada Messenger for the Web BETA at
http://ca.messenger.yahoo.com/webmessengerpromo.php


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2708 - Release Date: 02/25/10
20:57:00


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt status report [2010-02-14]

2010-02-16 Thread Gert Driesen
Hey Charlies,

Some quick responses:

NAnt.build
==
I don't consider NAnt.build internal. The nightly.xml and release.xml are
internal though, as these are used to build releases and nightly builds (or
CI).
In general, one should be able to build NAnt using its build file with the
previous official release. But the recommended approach is to 
bootstrap NAnt (using make/nmake) and then using that bootstrapped version
(with the NAnt build file) to build the full version. I think Ant uses the
same approach.

nant:scan-probing-paths
===
This function searches the probing paths - as defined in the NAnt
configuration file - of the current target framework for a given file
(generally an assembly). The advantage to using this function is that we can
move around (third-party) assemblies without affecting our build file(s).
For example:
We could have a given assembly located in lib/net/2.0 today, because it
contains code specific to .NET Framework 2.0 (hence we'd need a Mono
specific version as well).
If in a future release of that assembly that specific code is removed -
making this assembly also usable in Mono - then we could just move it to
lib/common/2.0 to make it available on Mono as well.
By using this function, we make sure we use that the (third-party) libraries
we use for building NAnt for a given target framework are the same libraries
that we use for running NAnt on that framework (CLR).

Linux/Mono support
==
It's ok if this is not high on your todo list, but you should keep it in
mind.
That way you don't introduce stuff that is not portable / cross-platform.

Gert

 -Original Message-
 From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
 Sent: dinsdag 16 februari 2010 4:43
To: Gert Driesen; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] NAnt status report [2010-02-14]

Hi Gert,

Thanks for the information. I apologize if I appear to be stumbling a bit.

More comments below... you feedback is much appreciated.

Charles



- Original Message 
 From: Gert Driesen gert.drie...@telenet.be
 To: Charles Chan cchan...@users.sourceforge.net;
nant-developers@lists.sourceforge.net
 Sent: Sun, February 14, 2010 11:10:00 PM
 Subject: RE: [nant-dev] NAnt status report [2010-02-14]
 
 Hey Charles,
 
 That function - which I consider to be internal - may indeed not be part
of
 any official release.

That is sort of what I figured and worried (see below).

 So in this case, you can only build NAnt with:
 * a nightly build (which hasn't been uploaded in quite a while due to
 scp/rsync issues with sourceforge)
 * a bootstrap of NAnt (though make/nmake)
 This last option is the one I'd recommend.

 If that's ok for you, I'd like you to revert the changes to the build file
 that removed the use of nant::scan-probing-paths.
 Use of this function gives us more flexibility as to the actual location
of
 some libraries.

I don't have a problem against it, but I just need to understand the
mechanics of how the whole thing works. I believe the build/test/release
process should be as simple as possible so any developers can pick it up --
fast. If it doesn't work out of the box, then most people probably will not
spend time to figure out how to use it. This is my personal experience and
probably echo a lot of other people. Also, there should be as little
dependency as possible, and when there is, it needs to be fully documented.
Anyone should be able to check out the code and go. This is also why I
favor the use of CI server, it gives immediate response, and helps checks
your code and the full build process. It also provides a secondary
configuration to test the build against. Of course, I understand there might
be reasons or difficulties that I am not aware of yet at this time, so I am
open to ideas.

Now back to the specific problem -- building NAnt with NAnt.
1) Is NAnt supposed to be built with make/nmake only? I guess my confusion
is that every project (that uses NAnt) has a .build file in the base dir.
However, building NAnt itself is probably different. Is NAnt.build internal?

 a) If 1) is true then: NAnt.build (nightly.xml and release.xml) is
meant for internal build/release only. In that case, these files should not
reside in the base folder. The average NAnt user does not need to be
bothered and therefore it should be moved to a sub-folder. 

 b) If 1) is false then: Users need to use NAnt.build and this is
currently problematic because building the latest NAnt requires a
non-released version of NAnt. I would suggest the following changes:
* Change the trunk version to 0.87
* In NAnt.build, detect the runtime version of NAnt. If version  0.86,
continue. Otherwise 
* Autodetect the platform, and use GNU make (linux) / nmake (windows) to
compile bootstrap NAnt. This will probably involve the exec task. Note,
however, we should not 'install' the bootstrap version.
* Use the bootstrap NAnt to complete the rest of the compile

Re: [nant-dev] NAnt status report [2010-02-14]

2010-02-16 Thread Gert Driesen
Hey Charles,

 

The bootstrap version only contains those assemblies that are required to
build the full version.

These assemblies are known to build on all supported CLR's .

However, once the bootstrap version is built - the full version is
immediately built using that bootstrap version.

You could use the bootstrap target of the (n)make to only build the
bootstrap version itself though.

 

Aren't the instructions in README.txt (in the root of CVS module, and source
distribution) clear about building NAnt ?

 

Gert

 

From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: dinsdag 16 februari 2010 21:35
To: Gert Driesen; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] NAnt status report [2010-02-14]

 

Gert,

A few more questions? Hope you don't mind ... :)

Charles

 

- Original Message 
From: Gert Driesen gert.drie...@telenet.be
To: Charles Chan cchan...@users.sourceforge.net;
nant-developers@lists.sourceforge.net
Sent: Tue, February 16, 2010 12:27:03 PM
Subject: RE: [nant-dev] NAnt status report [2010-02-14]

Hey Charlies,

Some quick responses:

 NAnt.build
 ==
 I don't consider NAnt.build internal. The nightly.xml and release.xml are
 internal though, as these are used to build releases and nightly builds
(or
 CI).
 In general, one should be able to build NAnt using its build file with the
 previous official release. But the recommended approach is to 
 bootstrap NAnt (using make/nmake) and then using that bootstrapped version
 (with the NAnt build file) to build the full version. I think Ant uses the
 same approach.

Thanks. I will experiment with this work flow and document it.
What is the difference between a bootstrap version and the full version of
NAnt? What is missing from the bootstrap version? docs? tests? 

 nant:scan-probing-paths
 

Thanks I will read.

 Linux/Mono support
 ==
 It's ok if this is not high on your todo list, but you should keep it in
mind.
 That way you don't introduce stuff that is not portable / cross-platform.

Definitely. Portability is very important to me as well. That's why I will
also test the process with Mono and Linux after I got the basics sorted out.

 

  _  

Be smarter than spam. See how smart SpamGuard is at giving junk email the
boot with the  http://ca.promos.yahoo.com/newmail/overview2/ All-new
Yahoo! Mail 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2690 - Release Date: 02/15/10
20:35:00

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt status report [2010-02-14]

2010-02-14 Thread Gert Driesen
Hey Charles,

That function - which I consider to be internal - may indeed not be part of
any official release.
So in this case, you can only build NAnt with:
* a nightly build (which hasn't been uploaded in quite a while due to
scp/rsync issues with sourceforge)
* a bootstrap of NAnt (though make/nmake)
This last option is the one I'd recommend.

If that's ok for you, I'd like you to revert the changes to the build file
that removed the use of nant::scan-probing-paths.
Use of this function gives us more flexibility as to the actual location of
some libraries.

Sorry if I haven't been very responsive yet, but I hope to make up for this.
Concerning your question about building on Linux: we actually have a linux
box at our disposal through sponsorship by AOE media.
I'll send you the details later (but don't hesitate to remind me if
necessary).

The reason why Gerry was not able to contact me, is because my corporate
e-mail address (which I used in NAnt sources) changed after a merger.
I'll update all sources when I find a idle spot.

Regards

Gert

-Original Message-
From: Charles Chan [mailto:cchan...@users.sourceforge.net] 
Sent: maandag 15 februari 2010 3:38
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] NAnt status report [2010-02-14]

FYI.

Based on the information from Gerry, I spend the past week trying to 'build
NAnt with NAnt'. The first order of business was to understand how the whole
thing works. After diving around at the code (adding more comments along the
way), I focused on NAnt.build...

(Long story short) 
After I determined the main tasks in the .build file, I just kept running
'nant' (command). Repeated, I keep getting errors similar to the one below:

Unknown function 'nant::scan-probing-paths'.
Expression: ${nant::scan-probing-paths('nunit.framework.dll')}

I could not find any information regarding this function on the website.
Although I could see the function in the latest trunk, but trunk is not a
(real) release. So in the end, to replicate an 'average' NAnt user, I
decided to install the last official release (0.86-beta1) and use that as
the basis for the build. After replacing all instances of
'scan-probing-paths' and fix it with the correct path, the 'build' target
finally works. I verified the changes both locally and on TeamCity
[http://teamcity.codebetter.com/project.html?projectId=project69]

Next steps (prioritized):
* The 'test' target also compiles and runs, but a few tests are failing.
Need to investigate.
* Look at nightly.xml to generate nightly releases.
* Look at release.xml to generate official releases.
* Generate additional docs / comments to help others in future.
* (Request from Leszek) Investigate 1) Mono and 2) Linux configuration. I am
thinking of openSuse Build Service, but needs more investigation?
[https://build.opensuse.org/]

Regards,
Charles



  __
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2688 - Release Date: 02/14/10
20:35:00


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] [INTRO] Self-introduction for Charles Chan

2010-02-12 Thread Gert Driesen
Hey Charles,

It's great to have new blood joining the NAnt team, but may I ask which 
project admin you contacted to become member ?

Regards,

Gert
--
From: Charles Chan cchan...@users.sourceforge.net
Sent: Thursday, February 11, 2010 4:23 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] [INTRO] Self-introduction for Charles Chan

 Hello fellow developers,

 I am the newest addition to the NAnt developers team, let me provide a 
 brief self introduction.

 Current Experience
 ==
 I am a senior software engineer  mobile team lead at my
 current employment. Mostly I use C/C++/Java code at work, but our 
 compilation
  release are handled by a combination of shell/NAnt/ant build
 scripts. Additional, we use Hudson for CI.

 Previous Experience
 ===
 In addition, I have worked on server-side development in the past, using 
 J2EE, XML, HTML,
 JavaScript, CSS, AJAX, SQL. I also have experience with C#.NET developing 
 desktop applications. In addition, I am familiar with various databases 
 such as Oracle, SQL Server, MySQL, etc

 Open Source Experience
 ==
 I have participated in other open
 source projects such as GoogleTest, Hudson, jTDS as well.

 Objective for joining NAnt
 ==
 1) A short 0.8x or 0.9x beta/rc release, follow by a stable 1.0 release -- 
 This is to ensure all the patches from the last few years are
 re-incorporated back into a common tree. It's double maintainence for
 company to have to keep a patched copy of NAnt locally in their SCM
 system. Besides, every contribution helps improve the general user 
 community.

 2) Add/Remove platform / solution support to keep up with current 
 technologies.

 2) Compare the changes that has been requested / or
 added in other builds systems -- Evaluate what makes sense to add in a 
 next release.

 What's been done
 =
 The first order of business for me was to find and setup a stable server 
 for generating CI builds and releases. Thanks to the folks at 
 TeamCity.CodeBetter.com, I was able to register an account for NAnt 
 project there.
 Take a look at 
 http://teamcity.codebetter.com/project.html?projectId=project69

 Help requests
 ==
 I am ready to generate a new NAnt release (eg. 0.87-rc1), and requires 
 some assistance. If any of you can provide some information, it would be 
 much appreciated.

 1) What is the proper way to make a release? -- On the CI server, I am 
 current using VS.NET with NAnt.sln. But where are the artifacts?

 2) On the NAnt homepage, I see the software is described compatible with 
 .NET
 1.0/1.1/2.0/3.5; Mono 1.0/2.0/3.5, etc... How does NAnt project
 produce one library and make sure it's compatible with all of the above
 platforms? Do you compile with the lowest common denominator (.NET 1.0)? 
 How do you ensure a library works with both .NET and Mono -- simply by
 assuming the CLR is consistently implemented on all platforms? Do you have 
 to compile on both Windows and Linux platforms?

 3) (related to #2) What is the difference between Target and Runtime 
 support? eg. .NET Compact Framework 1.0 only has support for Target, but 
 not Runtime. Does this simply mean NAnt can only used on a host PC to 
 compile .NET
 CF 1.0 project, and not available as a library to execute on a WM
 device?

 4) I see in the trunk, there are files named nighly.xml and 
 release.xml. These sound like they are a bootstrap process, can anyone 
 provide a highlevel overview of how they work? (I haven't read these in 
 much detail.)

 Cheers,
 Charles


  __
 Make your browsing faster, safer, and easier with the new Internet 
 Explorer® 8. Optimized for Yahoo! Get it Now for Free! at 
 http://downloads.yahoo.com/ca/internetexplorer/

 --
 SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
 Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
 http://p.sf.net/sfu/solaris-dev2dev
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] New developer wanting to help out

2009-09-08 Thread Gert Driesen
Hi Rasmus,

 

Feel free to post patches to the developer mailing list.

For isolated changes, you can even send me the modified source(s).

 

Great to have you on board!

 

Gert

 

From: Rasmus Jelsgaard [mailto:ras...@jelsgaard.com] 
Sent: dinsdag 8 september 2009 20:24
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] New developer wanting to help out

 

Hello,

 

I've found a couple of bugs/things I would like to enhance in this great
build tool, which I use heavily at work. I would like to contribute with bug
fixes etc. as soon as possible but I don't know how to get started. I've
already fixed an open issue but don't know how to submit the patch in the
proper way so a few pointers would be greatly appreciated :)

 

Regards,

Rasmus Jelsgaard

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.285 / Virus Database: 270.13.83/2352 - Release Date: 09/07/09
18:03:00

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Can we get a new NAnt version released, please?

2009-06-21 Thread Gert Driesen
Hi Scott,

 

I was hoping to find time for changes related to (embedded and linked)
resources, (extension) assembly isolation, namespace support and lots of
other stuff.

But it has become very hard for me to dedicate time slots to NAnt (due to
work, my daughter, .).

What you (or anyone else) can do, is more actively contribute to both
development and discussion.

 

I've removed the Wiki link in CVS, it'll be gone next time I sync.

 

Gert

 

From: Scott White [mailto:scott.w.wh...@gmail.com] 
Sent: zondag 21 juni 2009 21:01
To: Bruce Cran
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Can we get a new NAnt version released, please?

 

I totally agree with this.  What would it take to release, even a new beta.
Is there any way the rest of us can get involved in help in this effort?
Also there's some broken links on the front page that should be fixed too
(click the Wiki link).

 

Thanks,

Scott

On Sun, Jun 21, 2009 at 3:55 AM, Bruce Cran bruce.c...@gmail.com wrote:

Since versions before 1.0 are generally considered beta anyway, could
we get a new version number please? I can't believe how many betas and
release candidates there have been for this project when it still
hasn't reached 1.0!  At the moment anyone checking the project page
would think this project was dead and that MSBuild has won; that's a
real shame because NAnt is awesome and I still think it's the better
build solution.

--
Bruce

On Fri, 12 Jun 2009 08:00:16 -0700  Gert Driesen wrote:
 Hi Leszek,

 I agree that a new version should be released.
 I would first like to release a new beta/release candidate though.

 Now only to find time ... :(

 Gert

--
From: Leszek Ciesielski skol...@gm...
Sent: Friday, June 12, 2009 10:58 AM
To: nant-develop...@li...
Subject: [nant-dev] Can we get a new NAnt version released, please?

 Hi,

 NAnt has been in 0.86 Beta version for two years. I guess time has
 come to promote it to Release status? Many people are reluctant to
 use software labeled Beta, and grow even more suspicious when told
 to install nightly. Gert, would you care to comment please?

 Regards,

 Leszek 'skolima' Ciesielski



--
 Crystal Reports - New Free Runtime and 30 Day Trial
 Check out the new simplified licensing option that enables unlimited
 royalty-free distribution of the report engine for externally facing
 server and web deployment.
 http://p.sf.net/sfu/businessobjects
 ___
 nant-developers mailing list
 nant-develop...@li...
 https://lists.sourceforge.net/lists/listinfo/nant-developers




--
Are you an open source citizen? Join us for the Open Source Bridge
conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference:
$250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.o
rg
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.285 / Virus Database: 270.12.80/2187 - Release Date: 06/19/09
06:53:00

--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Can we get a new NAnt version released, please?

2009-06-12 Thread Gert Driesen
Hi Leszek,

I agree that a new version should be released.
I would first like to release a new beta/release candidate though.

Now only to find time ... :(

Gert

--
From: Leszek Ciesielski skol...@gmail.com
Sent: Friday, June 12, 2009 10:58 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Can we get a new NAnt version released, please?

 Hi,

 NAnt has been in 0.86 Beta version for two years. I guess time has
 come to promote it to Release status? Many people are reluctant to
 use software labeled Beta, and grow even more suspicious when told
 to install nightly. Gert, would you care to comment please?

 Regards,

 Leszek 'skolima' Ciesielski

 --
 Crystal Reports - New Free Runtime and 30 Day Trial
 Check out the new simplified licensing option that enables unlimited
 royalty-free distribution of the report engine for externally facing
 server and web deployment.
 http://p.sf.net/sfu/businessobjects
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 


--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] PostBuildEvent

2009-01-20 Thread Gert Driesen
Hi Manjusha,

No, this is not something we currently support in the solution task.

Gert

From: Lokhande, Manjusha 
Sent: Tuesday, January 20, 2009 6:44 AM
To: nant-developers@lists.sourceforge.net 
Subject: [nant-dev] PostBuildEvent


Hi,

 

I have a PostBuildEvent defined in my .csproj file.

But I do not wish to run this event after completing the build through NAnt. 
How could I achieve this with NAnt?

Is there any way to bypass PostBuildEvent using NAnt build script?

In case of MSBuild, a PostBuildEvent can be bypassed simply passing an empty 
string to a parameter named PostBuildEvent (/p:PostBuildEvent=).

Is anybody aware of such thing in NAnt?

Please HELP!

 

Thanks,

Manjusha Lokhande







Important Notice to Recipients: 
It is important that you do not use e-mail to request, authorize or effect the 
purchase or sale of any security or commodity, to send fund transfer 
instructions, or to effect any other transactions. Any such request, orders, or 
instructions that you send will not be accepted and will not be processed by 
Morgan Stanley. 





--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword 





___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt support für 64Bit and new framew ork sdk version

2009-01-10 Thread Gert Driesen
Hi Steve,

I've added support for Windows SDK 6.1 to CVS.

I don't think we explicitly need to check the Wow6432Node registry keys.

I tried to run NAnt both compiled targeting .NET 1.0 (which means it will
run in WOW64) and .NET 2.0 on Vista x64, and had no problems.

I'll try to get a new nightly build up tomorrow, but I've been struggling
with cygwin issues uploading files using the new sourceforge shell service.

Best regards,

Gert

-Original Message-
From: Steve Wagner [mailto:li...@lanwin.de] 
Sent: vrijdag 9 januari 2009 17:13
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] NAnt support für 64Bit and new framework sdk version

To support 3.5 builds on 64 bit windows system and also to support the
new framework sdk version, nant needs to change the NAnt.exe.config
Framework name=net-3.5 to:

project
 readregistry
property=installRoot
key=SOFTWARE\Microsoft\.NETFramework\InstallRoot
hive=LocalMachine /
 readregistry
property=sdkInstallRoot
key=SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v6.1\WinSDKNetFxTools\InstallationFolder
hive=LocalMachine
failonerror=false /
 readregistry
property=sdkInstallRoot
key=SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v6.0A\WinSDKNetFxTools\InstallationFolder
hive=LocalMachine
failonerror=false /
 readregistry
property=sdkInstallRoot
key=SOFTWARE\Wow6432Node\Microsoft\Microsoft
SDKs\Windows\v6.1\WinSDKNetFxTools\InstallationFolder
hive=LocalMachine
failonerror=false /
 readregistry
property=sdkInstallRoot
key=SOFTWARE\Wow6432Node\Microsoft\Microsoft
SDKs\Windows\v6.0A\WinSDKNetFxTools\InstallationFolder
hive=LocalMachine
failonerror=false /
/project

Could someone add this to nant and make a new nightly build?

Steve


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com 
Version: 8.0.175 / Virus Database: 270.10.3/1877 - Release Date: 1/5/2009
7:20 PM


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Testing a Custom Task

2008-10-26 Thread Gert Driesen
Hey Andrew,

Most of the initialization is started here:

void Initialize(XmlNode elementNode, PropertyDictionary properties,
FrameworkInfo framework)
in NAnt.Core.Element

I'd suggest debugging NAnt running a simple project if you want to learn
more.

If you have any specific questions, I'll be glad to help.

Gert

-Original Message-
From: Schley Andrew Kutz [mailto:[EMAIL PROTECTED] 
Sent: zondag 26 oktober 2008 16:56
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Testing a Custom Task

All of the examples I have found in NAnt and NAnt-Contrib begin and
end with the base test class and executing a project. I am not
interested in executing the project as I know the execution will work
if the properties and build elements are loaded properly. What I am
interested in is parsing XML to see if the aforementioned items *do*
load as expected. This is where I am having trouble; I cannot figure
out how to parse the XML into a task. I have attempted the
InitializeXml method with the necessary parameters, but I keep getting
an Object not initialized exception on the AttributeConfigurator's
ctor.

Any and all assistance is appreciated. Thanks!

-- 
-a

condensing fact from the vapor of nuance

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] question about different methods to build nant source

2008-08-22 Thread Gert Driesen
Hey Shovavnik,

 

The (n)make method is used for bootstrapping NAnt; meaning, building a
minimal version NAnt -without relying on NAnt itself - that can be used to
build the full version of NAnt.

 

That full version is actually built using the NAnt.build file. That build
file is used to build both non-release and release versions of NAnt.

 

The VS solution is only supplied to easy browsing the NAnt sources. I never
use it to actually build NAnt, but it should still work.

 

You get the compile warning/error because the conditional compilation flags
for .NET 2.0 have not been set. Set the NET_2_0 define and try again.

 

Let me know if there's anything else you need.

 

Gert

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
shovavnik
Sent: donderdag 21 augustus 2008 23:44
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] question about different methods to build nant source

 

Hi all,

Just starting out with the NAnt source to see how things work under the hood
and maybe to contribute.

I noticed that the readme gives the nmake command line, which works great
(even on Vista as long as you open the command prompt as an administrator).
But there is also a NAnt.build file in the source folder, which also works
great.

Also, in VS 2008, the build fails with these errors:
Error1Warning as Error:
'System.Runtime.InteropServices.Marshal.GetTypeLibName(System.Runtime.Intero
pServices.UCOMITypeLib)' is obsolete: 'Use
System.Runtime.InteropServices.Marshal.GetTypeLibName(ITypeLib pTLB)
instead. http://go.microsoft.com/fwlink/?linkid=14202
http://go.microsoft.com/fwlink/?linkid=14202ID=011 ID=011.'
C:\Projects\NAnt\src\NAnt.VSNet\WrapperReferenceBase.cs36020
NAnt.VSNet
Error2Warning as Error:
'System.Runtime.InteropServices.UCOMITypeLib' is obsolete: 'Use
System.Runtime.InteropServices.ComTypes.ITypeLib instead.
http://go.microsoft.com/fwlink/?linkid=14202'
C:\Projects\NAnt\src\NAnt.VSNet\WrapperReferenceBase.cs36044
NAnt.VSNet
Error3Metadata file
'C:\Projects\NAnt\build.VS.NET\NAnt.MSNet\NAnt.MSNetTasks.dll' could not be
foundNAnt.Console
Error4Metadata file
'C:\Projects\NAnt\build.VS.NET\NAnt.VSNet\NAnt.VSNetTasks.dll' could not be
foundNAnt.Console
Warning5Found conflicts between different versions of the same
dependent assembly.NAnt.Console

So, in theory, there seem to be 3 different build methods to build the NAnt
source.

The question is, why are all 3 of these methods needed? Isn't this
unnecessary duplication of functionality? Is the NAnt.build more of a
self-compiling proof-of-concept?

Regards,
shovavnik

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Setting message level output from exec programs

2008-07-23 Thread Gert Driesen
Hey Robin,

 

Currently, the exec task will log all output that the external process
writes to stderr as warnings. I don't think we should consider all output to
stderr as actual errors.

 

I'd suggest fixing your buildhelper to return a non-zero exit code when
execution fails.

 

Gert

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robin
McKenzie
Sent: woensdag 23 juli 2008 12:52
To: 'nant-developers@lists.sourceforge.net'
Subject: [nant-dev] Setting message level output from exec programs

 

 

Hi,

 

I'm interested in finding out how an external program, run through the exec
program= NAnt command can produce message elements in the log file with
a level other than Warning.

 

My build file contains:

exec program=${BuildHelper.exe}

arg
value=-assembly:D:\data\Build\BuildHelperLib.dll/

arg value=-type:Acturis.HelperLib.XmlFileUtil/

arg value=-method:AttributeTransformXmlFile/

arg
value=-param:${generateConfig.transform.XmlFile}/

arg
value=-param:${generateConfig.source.XmlFile}/

arg
value=-param:${generateConfig.outputConfigXmlFile}/

arg
value=-param:${generateConfig.transform.Key}/

arg value=-param:${generateConfig.env}/

/exec

 

And the output generated is:

  task name=exec

message level=Info![CDATA[Invoking
D:\data\Build\BuildHelperLib.dll : SNIP...]]/message

message level=Warning![CDATA[Unhandled Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by
the target of an invocation. --- System.NullReferenceException: Object
reference not set to an instance of an object.]]/message

message level=Warning![CDATA[at
Acturis.HelperLib.XmlAttributeTransform.ApplyAttributeValueOverride(SNIP)]]
/message

message level=Warning![CDATA[at
Acturis.HelperLib.XmlAttributeTransform.TransformXml(SNIP)]]/message

message level=WarningLots more warnings./message

duration13296.7899/duration

  /task

 

However, I wish for the build to break, and the Warnings above should be
thrown as Errors.

 

The BuildHelper.exe program was written for us by a contractor who has since
left, but the code is fairly simple C#.NET code.  The NullReferenceException
has been thrown by the .NET framework, but I can't see how it has been
determined to be a Warning rather than an Error.

 

Alternatively, if I can set the exec to failOnWarning that would be a
less satisfactory, but nonetheless workable solution.

 

Any ideas would be much appreciated.

 

Kind Regards,

 

Robin McKenzie 

acturis ltd | connected thinking

 

 

  _  

Winner of Service Provider of the Year 2007 at the British Insurance Awards
Winner of Service Provider of the Year 2006 at the Insurance Times Awards

Please consider the environment before printing this e-mail

This e-mail and any files transmitted with it are confidential and/or
privileged and protected by the laws of copyright. They are for the intended
recipient only. If you are not the intended recipient, you must not use,
review, distribute, disclose, alter, print, copy, transmit or rely on this
e-mail and any file transmitted with it. If you have received this e-mail
and any file transmitted with it in error please notify the sender.


Acturis Limited is registered in England and Wales. Registered Office:
Courtyard Suite, 100 Hatton Garden, London, EC1N 8NX. Company Number:
3998084.


___
This message is privileged, confidential and is protected by the laws of
copyright. 
If you have reason to believe that you are not the intended recipient, 
please let us know immediately at [EMAIL PROTECTED]

This email has been scanned by the MessageLabs Email Security System.

___

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] zip task Problem loading SharpZipLib

2008-06-22 Thread Gert Driesen
Mark,
 
We ship with #ziplib v0.85.1.271, but the directory in which it's stored
changed since earlier versions of NAnt.
 
You probably extract the lastest version of NAnt into a directory containing
an older version.
 
Gert

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Snyder
Sent: donderdag 19 juni 2008 23:04
To: 'nant-developers@lists.sourceforge.net'
Subject: [nant-dev] zip task Problem loading SharpZipLib



I downloaded the latest version of NAnt and NAntContrib, and tried to use a
simple zip task in my NAnt script.

 

The version of SharpZipLib.dll that comes with NAnt, in path\NAnt\bin\lib,
is 0.84.0.0.  

 

I tried downloading the latest version of SharpZipLib, renaming
ICSharpCode.SharpZipLib.dll to ICSharpCode.SharpZipLib.dll.bak, and putting
the new version in its place, and the new file is version 0.85.4.369.

 

Looking at the error reported below (with Fusion logging turned on for extra
verbosity), apparently NAnt.exe depends upon version 0.85.1.271 of
SharpZipLib and won't load either of the above versions.

 

Anybody know how to resolve this issue?

 

Thanks,

Mark

 

Email me at snyderma at duckcreektech dot com.

 

When I try to build my target, I get:

 

BUILD FAILED

 

INTERNAL ERROR

 

System.IO.FileLoadException: Could not load file or assembly
'ICSharpCode.SharpZ

ipLib, Version=0.85.1.271, Culture=neutral, PublicKeyToken=1b03e6acf1164f73'
or

one of its dependencies. The located assembly's manifest definition does not
mat

ch the assembly reference. (Exception from HRESULT: 0x80131040)

File name: 'ICSharpCode.SharpZipLib, Version=0.85.1.271, Culture=neutral,
Public

KeyToken=1b03e6acf1164f73'

   at NAnt.Compression.Tasks.ZipTask.ExecuteTask()

   at NAnt.Core.Task.Execute()

   at NAnt.Core.Target.Execute()

   at NAnt.Core.Project.Execute(String targetName, Boolean
forceDependencies)

   at NAnt.Core.Project.Execute()

   at NAnt.Core.Project.Run()

 

=== Pre-bind state information ===

LOG: User = EngBuild3X\Administrator

LOG: DisplayName = ICSharpCode.SharpZipLib, Version=0.85.1.271,
Culture=neutral,

 PublicKeyToken=1b03e6acf1164f73

 (Fully-specified)

LOG: Appbase = file:///C:/Program Files/Nant/bin/

LOG: Initial PrivatePath = lib;lib\net\2.0;lib\common\neutral

Calling assembly : NAnt.CompressionTasks, Version=0.86.2898.0,
Culture=neutral,

PublicKeyToken=null.

===

LOG: This bind starts in default load context.

LOG: Using application configuration file: C:\Program
Files\Nant\bin\NAnt.exe.co

nfig

LOG: Using machine configuration file from
C:\WINDOWS\Microsoft.NET\Framework\v2

.0.50727\config\machine.config.

LOG: Post-policy reference: ICSharpCode.SharpZipLib, Version=0.85.1.271,
Culture

=neutral, PublicKeyToken=1b03e6acf1164f73

LOG: Attempting download of new URL file:///C:/Program
Files/Nant/bin/ICSharpCod

e.SharpZipLib.DLL.

LOG: Attempting download of new URL file:///C:/Program
Files/Nant/bin/ICSharpCod

e.SharpZipLib/ICSharpCode.SharpZipLib.DLL.

LOG: Attempting download of new URL file:///C:/Program
Files/Nant/bin/lib/ICShar

pCode.SharpZipLib.DLL.

WRN: Comparing the assembly name resulted in the mismatch: Minor Version

ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing
terminated.

 

 

 

Please send bug report to [EMAIL PROTECTED]

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] 3.5 Framework with yesterday's CVS Code

2008-05-01 Thread Gert Driesen
Eric,
 
We do not yet support .NET Framework 3.5 for the solution task.
 
In order to support both .NET 2.0 and 3.5, we need to use reflection for the
MSBuild assemblies and we have problems loading the 3.5 version of the
MSBuild assemblies.
 
I don't recall the exact details, but I'll contact the developer that was
working on this (Martin Aliger) to get a status update.
 
Gert

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Fetzer
Sent: donderdag 1 mei 2008 20:19
To: NAnt Developers
Subject: [nant-dev] 3.5 Framework with yesterday's CVS Code


It appears to be building off of the 2.0 csc.exe instead of the 3.5 csc.exe.
Here's my target:
 
  target name=build depends=getLatest
property name=nant.settings.currentframework value=net-3.5/
solution configuration=release verbose=true  
  projects
 include name=${build.dir}\MyProject\MyProject.csproj /
  /projects
  referenceprojects
 includes
name=${build.dir}\MyProjectReference\MyProjectReference.csproj /
  /referenceprojects
  assemblyfolders
include name=D:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PublicAssemblies /
  /assemblyfolders
/solution
  /target
 
Here's my output in the log:
 

[solution] C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig
/unsafe- /checked- /nowarn:1701,1702 /nostdlib- /errorreport:prompt /warn:4
/baseaddress:285212672 /define:TRACE
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.configuratio
n.dll /reference:C:\Program Files\Reference
Assemblies\Microsoft\Framework\v3.5\System.Core.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll
/debug- /filealign:4096 /optimize+ /out:obj\release\MyProject.dll
/target:library /warnaserror- AssemblyInfo.cs myFile1.cs myFile2.cs
myFile3.cs myFile4.cs

 

I never see it switch over to the proper framework and it definitely uses
the wrong csc...  The only thing I see it using for 3.5 is system.core.dll.
Seems I could hack the nant.exe.config file to get this to work.  Any help?

 

Thanks,

Eric


  _  

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8
HDtDypao8Wcj9tAcJ it now.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Upgrade to latest nightly build

2008-04-17 Thread Gert Driesen
Eric,
 
Can you send me a small repro for this issue?
 
Thanks!
 
Gert 
  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Fetzer
Sent: woensdag 16 april 2008 23:47
To: NAnt Developers
Subject: [nant-dev] Upgrade to latest nightly build


I upgraded to try out the 3.5 stuff again.  Well, in my build, I start with
a 2.0 project build and it no longer works.  Right before building this
project, I set: property name=nant.settings.currentframework
value=net-2.0/.  With the 86rc1, this builds fine.  With 2/10 nightly, I
get the error:
 
System.NullReferenceException: Object reference not set to an
instance of an object.
   at NAnt.MSBuild.MSBuildConfiguration..ctor(MSBuildProject
project, Project msproj, Configuration projectConfig) in
d:\Source\nant-20080210T102007Z\src\NAnt.MSBuild\MSBuildConfiguration.cs:lin
e 52
   at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution,
String projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
DirectoryInfo outputDir) in
d:\Source\nant-20080210T102007Z\src\NAnt.MSBuild\MSBuildProject.cs:line 104
   at
NAnt.MSBuild.MSBuildProjectProvider.GetInstance(SolutionBase solution,
String projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
DirectoryInfo outputDir) in
d:\Source\nant-20080210T102007Z\src\NAnt.MSBuild\MSBuildProjectProvider.cs:l
ine 45
   at NAnt.VSNet.ProjectFactory.CreateProject(SolutionBase
solution, SolutionTask solutionTask, TempFileCollection tfc, GacCache
gacCache, ReferencesResolver referencesResolver, DirectoryInfo outputDir,
String projectPath) in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\ProjectFactory.cs:line 174
   at NAnt.VSNet.ProjectFactory.LoadProject(SolutionBase
solution, SolutionTask solutionTask, TempFileCollection tfc, GacCache
gacCache, ReferencesResolver referencesResolver, DirectoryInfo outputDir,
String path) in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\ProjectFactory.cs:line 100
   at NAnt.VSNet.SolutionBase.LoadProjects(GacCache gacCache,
ReferencesResolver refResolver, Hashtable explicitProjectDependencies) in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\SolutionBase.cs:line 392
   at NAnt.VSNet.SolutionBase..ctor(SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver)
in d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\SolutionBase.cs:line 45
   at NAnt.VSNet.GenericSolution..ctor(SolutionTask
solutionTask, TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver) in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\GenericSolution.cs:line 36
   at NAnt.VSNet.SolutionFactory.LoadSolution(SolutionTask
solutionTask, TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver) in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\SolutionFactory.cs:line 63
   at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in
d:\Source\nant-20080210T102007Z\src\NAnt.VSNet\Tasks\SolutionTask.cs:line
454
   at NAnt.Core.Task.Execute() in
d:\Source\nant-20080210T102007Z\src\NAnt.Core\Task.cs:line 186
   at NAnt.Core.Target.Execute() in
d:\Source\nant-20080210T102007Z\src\NAnt.Core\Target.cs:line 247
   at NAnt.Core.Project.Execute(String targetName, Boolean
forceDependencies) in
d:\Source\nant-20080210T102007Z\src\NAnt.Core\Project.cs:line 917
   at NAnt.Core.Project.Execute() in
d:\Source\nant-20080210T102007Z\src\NAnt.Core\Project.cs:line 869
   at NAnt.Core.Project.Run() in
d:\Source\nant-20080210T102007Z\src\NAnt.Core\Project.cs:line 954

Please send bug report to [EMAIL PROTECTED]
 
 
 
 
Any help?
 
Thanks,
Eric

  _  

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8
HDtDypao8Wcj9tAcJ it now.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] FW: System.Data.OracleClient assembly no longer resolved(different behaviour 0.85 v 0.86b1)

2008-04-16 Thread Gert Driesen
Eric,

For .NET, we now use an explicit set of assemblies that we can automatically
resolve to a full path.

This set can be configured in the NAnt.exe.config file.

I have now added the System.Data.OracleClient assembly.

You can double-check the configuration file to make sure our list is
complete now.

Gert

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erik
Renes
Sent: woensdag 16 april 2008 18:33
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] FW: System.Data.OracleClient assembly no longer
resolved(different behaviour 0.85 v 0.86b1)

Hi all, 

When upgrading Nant to the latest version today, I noticed that a lot of my
previously working build scripts were failing. Compile errors arose from the
fact that System.Data.OracleClient.dll wasn't referenced.

Further investigation showed that nant 0.85 resolves the following: 
include name=System.Data.OracleClient.dll / To be:
 C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Data.OracleClient.dll

0.86 beta 1 fails to resolve the assembly.

When pursuing this in code I found that Resolving assemblies in the
Framework Directory had moved from AssemblyFileSet in NAnt.DotNet to
FrameworkInfo in Nant.Core, also see:
http://nant.cvs.sourceforge.net/nant/nant/src/NAnt.DotNet/Types/AssemblyFile
Set.cs?r1=1.7r2=1.8

When looking in FrameworkInfo, I found that the new code did not reflect the
original code: 
http://nant.cvs.sourceforge.net/nant/nant/src/NAnt.Core/FrameworkInfo.cs?r1=
1.22r2=1.23
(look for ResolveAssembly).

Locally, I have added the original code in AssemblyFileSet again, this has
successfully solved my problem. However, this means that there is either a
bug in 0.86, or an intended change in behaviour. Given the CVS commit
comments, I doubt this was an intentional change. 
Before reporting this as a bug, I would like to confirm whether or not this
change in behaviour was intentional?

If required, it would be possible for me to include a very small buildfile
that shows the problem.

Best regards,
Erik Renes


-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss
this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao
ne
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] cannot build NAnt

2008-01-29 Thread Gert Driesen
Paul,

You'll need to use the bootstrap version of NAnt to build NAnt 0.86.

To create the bootstrap version:

(linux / cygwin)
$ make bootstrap
or 
(windows)
$ nmake -f Makefile.nmake bootstrap

Hope this helps,

Gert
- Original Message - 
From: paul [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Tuesday, January 29, 2008 2:58 PM
Subject: [nant-dev] cannot build NAnt


 Hi,
 
 I am trying to build on my computer, but I can't get it to build correctly.
 I have both visual studio 2003 and 2005 installed, but I use the 2003 
 command promt to build.
 In the nant-nightly directory (were also NAnt.sln is) I simply start 
 NAnt in to build. At first I had the problem that my LIB environment 
 variable contained a reference to a non-existant directory, causing NAnt 
 to fail. After removing this entry from my vcvars32.bat it now at least 
 starts compiling. It fails however when attempting to build  
 NAnt.Console.Build. with the following message:
 
   
 D:\projects\nant-0.86-nightly-2007-12-19\src\NAnt.Console\NAnt.Console.build(16,18):
   Operator '=' cannot be applied to arguments of type 
 'System.Version' and 'System.Version'.
Expression: 
 ${framework::get-family(framework::get-target-framework())== 'net' and 
 framework::get-version(framework::get-target-framework()) = 
 version::parse('2.0')}
 
 I am using NAnt 0.85 for building.
 
 What am I doing wrong here?
 
 Any help is appreciated
 
 Paul
 
 
 
 
 
 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] NAnt 0.86 Beta 1 is available

2007-12-08 Thread Gert Driesen
The first beta for NAnt 0.86 is available NOW !
 
This release focuses on extending our already strong support for multiple
target frameworks, bringing improved flexibility and performance.
 
As of this release, our framework support chart looks like this:
 
Framework Target  Runtime

.NET Framework 1.0  **  
.NET Framework 1.1  **  
.NET Framework 2.0  **  
.NET Framework 3.5  **  
.NET Compact Framework 1.0  *   
.NET Compact Framework 2.0  *   
Mono 1.0 Profile**  
Mono 2.0 Profile**  
Mono 3.5 Profile**  
Moonlight 2.0   *   
Shared Source CLI 1.0   *   
Silverlight 2.0 *   
 
A complete list of changes and new features is available here:
http://nant.sourceforge.net/release/0.86-beta1/releasenotes.html
 
Binary and source distributions are available for immediate download from:
http://sourceforge.net/project/showfiles.php?group_id=31650 
 
Instruction for checking out sources from CVS are available here:
http://sourceforge.net/cvs/?group_id=31650
 
The CVS tag for NAnt 0.86 Beta 1 is:
rel-0-86-beta1
 
Discussion of NAnt occurs on the mailing list at
[EMAIL PROTECTED]
Bugs can be reported using the Bug Tracker at
http://sourceforge.net/projects/nant.
 
About NAnt: 
NAnt is a free .NET build tool, allowing applications to be built targeting
both Microsoft .NET and Mono while supporting both Windows and Linux
platforms.
 
Check the NAnt homepage for additional info at http://nant.sourceforge.net.



-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Sealed ResourceFileSet and Xml File attribute

2007-11-29 Thread Gert Driesen
Hi Dries,

There's no real reason why ResourceFileSet is sealed, so I'll change that.

Gert 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dries
Samyn
Sent: woensdag 28 november 2007 22:42
To: nant-developers@lists.sourceforge.net
Cc: Mark Reid
Subject: [nant-dev] Sealed ResourceFileSet and Xml File attribute

Hi,

We are working on an open source project, a tool to aid the
build/test/documentation process. This will come in the form of a set of
nAnt templates packaged up with the required binaries (nAnt, nUnit, nCover,
nCoverExplorer ...) to provide a one click solution.
Anyway, as party of our solution, we wanted to provide a non-intrusive and
optional way of integrating with visual studio project files. We achieved
this by implementing a BluePrintFileset task that supports a XmlInclude
element. This allows you to pass an XPath expression (and optionally a path
xslt file to transform the xml file before applying the XPath expression).
This allows something like this in the nAnt file:

blueprintfileset id=sources
   xmlinclude src=${path.src.project.csproj}
xpath=/ns:Project/ns:ItemGroup/ns:Compile/@Include
 namespaces
   namespace prefix=ns
uri=http://schemas.microsoft.com/developer/msbuild/2003; /
 /namespaces
   /xmlinclude
 /blueprintfileset

And this can be used in the compile task.

This works very well so far, but we have one issue. We realised later on the
ResourceFileset is a specialised type. So we thought of refactoring our code
to also provide a special case of this. However, we noticed this class is
sealed. We changed this and re-compiled and tested our solution and all
seems to work.
So we have a couple of questions. Firstly, is there any reason why this
class is sealed?
Secondly, we would obviously prefer to not have to use a bespoke
version of nAnt. So would there be any way we could commit this change if
there would be no specific reason for this to be sealed? Or, is there any
scope to add the XmlInclude element to the standard Fileset? It may be
generally quite useful functionality?

I tried to attached a copy of the task for reference, but the email didn't
get through, so if anybody wants a copy, let me know and I'll email it or
upload it somewhere.

Dries.



-
SF.Net email is sponsored by: The Future of Linux Business White Paper from
Novell.  From the desktop to the data center, Linux is going mainstream.
Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] [NAnt-users] Strict execution of managed applications

2007-11-16 Thread Gert Driesen
Erich,
 
I haven't yet released a nightly build containing this features, but will do
so later today.
 
If you're building from CVS then you already have access to the goodies ...
 
Was I you that I discussed this feature with once ?
 
Gert

  _  

From: Erich Eichinger [mailto:[EMAIL PROTECTED] 
Sent: vrijdag 16 november 2007 16:44
To: Gert Driesen; [EMAIL PROTECTED];
nant-developers@lists.sourceforge.net
Subject: RE: [NAnt-users] Strict execution of managed applications


Hi,
 
Cool! Thanks a lot - I'll give it a shot on our Spring.NET codebase asap.
 
keep up the great work!
 
cheers,
Erich


  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen
Sent: Friday, November 16, 2007 2:16 PM
To: [EMAIL PROTECTED]
Cc: nant-developers@lists.sourceforge.net
Subject: [NAnt-users] Strict execution of managed applications


Hi,
 
Today, I've finally introduced support for running a Managed application on
a specific version of a CLR.
 
We've been supporting running an application on a given CLR for quite a
while now, but we did not provide direct support for forcing an application
to run on a specific CLR version.
 
Meaning, you could not take an application compiled against .NET 1.1 and
force it to run on the .NET 2.0 CLR.
 
Well, you could do it by modifying or creating an application configuration
file for that application or by using construct specific for a given CLR
(eg. using COMPLUS_VERSION environment variable for the MS CLR), but there
was no fexible and portable mechanism to achieve this.
 
Now there is:
 
project default=run-tests
property name=supported.frameworks
value=net-1.1,net-2.0,mono-1.1,mono-2.0 /
 
target name=run-tests depends=compile
foreach property=framework item=String
in=${supported.frameworks} delim=,
if test=${framework::exists(framework)}
property name=nant.settings.currentframework
value=${framework} /
call target=test /
/if
/foreach
/target
 
target name=test
exec program=nunit-console.exe managed=strict
arg value=/noshadow /
arg file=Cegeka.HealthFramework.Tests.dll /
/exec
/target


target name=compile
csc ... /
/target
/project
 
This small (and incomplete) example shows how to use nunit-console to run
unit tests against a set of different CLR's.
 

The trick here is the value of the managed attribute on the exec task.
By setting it to strict, you instruct the task to run the application in
Strict mode.
 
Developers extending NAnt, can achieve the same result for tasks deriving
from ExternalProgramBase.by changing the value of the Managed property.
 
What this Strict mode means for a given target framework is configured in
the NAnt configuration file. 
 
Let's take the framework definition for the Mono 2.0 profile as an example:
 
framework name=mono-2.0 ...
runtime
probing-paths
directory name=lib/mono/2.0 /
directory name=lib/mono/neutral /
directory name=lib/common/2.0 /
directory name=lib/common/neutral /
/probing-paths
modes
auto
engine program=${runtimeEngine} /
environment
variable name=PATH
path=${path::combine(sdkInstallRoot, 'bin')};%PATH% /
variable name=MONO_CFG_DIR
path=${configDir};%MONO_CFG_DIR% /
/environment
/auto
strict
engine program=${runtimeEngine}
arg value=--runtime=v2.0.50727 /
/engine
environment
variable name=PATH
path=${path::combine(sdkInstallRoot, 'bin')};%PATH% /
variable name=MONO_CFG_DIR
path=${configDir};%MONO_CFG_DIR% /
/environment
/strict
/modes

/runtime
...

/framework
 
For Mono, the runtime can be instructed to forced to run an application
against a specific version of the runtime by using the --runtime
command-line option.
 
By looking at the runtime configuration section for the Mono 2.0 profile,
it's clear that the only difference between the auto and the strict mode
is exactly that additional command-line option.
 
As you can see there's no magic code involved: everything can be fully
configured in the NAnt configuration file.
 
If you have any questions or remarks regarding this new feature, just let me
know.
 
Gert

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] Strict execution of managed applications

2007-11-16 Thread Gert Driesen
Hi,
 
Today, I've finally introduced support for running a Managed application on
a specific version of a CLR.
 
We've been supporting running an application on a given CLR for quite a
while now, but we did not provide direct support for forcing an application
to run on a specific CLR version.
 
Meaning, you could not take an application compiled against .NET 1.1 and
force it to run on the .NET 2.0 CLR.
 
Well, you could do it by modifying or creating an application configuration
file for that application or by using construct specific for a given CLR
(eg. using COMPLUS_VERSION environment variable for the MS CLR), but there
was no fexible and portable mechanism to achieve this.
 
Now there is:
 
project default=run-tests
property name=supported.frameworks
value=net-1.1,net-2.0,mono-1.1,mono-2.0 /
 
target name=run-tests depends=compile
foreach property=framework item=String
in=${supported.frameworks} delim=,
if test=${framework::exists(framework)}
property name=nant.settings.currentframework
value=${framework} /
call target=test /
/if
/foreach
/target
 
target name=test
exec program=nunit-console.exe managed=strict
arg value=/noshadow /
arg file=Cegeka.HealthFramework.Tests.dll /
/exec
/target

target name=compile
csc ... /
/target
/project
 
This small (and incomplete) example shows how to use nunit-console to run
unit tests against a set of different CLR's.
 
The trick here is the value of the managed attribute on the exec task.
By setting it to strict, you instruct the task to run the application in
Strict mode.
 
Developers extending NAnt, can achieve the same result for tasks deriving
from ExternalProgramBase.by changing the value of the Managed property.
 
What this Strict mode means for a given target framework is configured in
the NAnt configuration file. 
 
Let's take the framework definition for the Mono 2.0 profile as an example:
 
framework name=mono-2.0 ...
runtime
probing-paths
directory name=lib/mono/2.0 /
directory name=lib/mono/neutral /
directory name=lib/common/2.0 /
directory name=lib/common/neutral /
/probing-paths
modes
auto
engine program=${runtimeEngine} /
environment
variable name=PATH
path=${path::combine(sdkInstallRoot, 'bin')};%PATH% /
variable name=MONO_CFG_DIR
path=${configDir};%MONO_CFG_DIR% /
/environment
/auto
strict
engine program=${runtimeEngine}
arg value=--runtime=v2.0.50727 /
/engine
environment
variable name=PATH
path=${path::combine(sdkInstallRoot, 'bin')};%PATH% /
variable name=MONO_CFG_DIR
path=${configDir};%MONO_CFG_DIR% /
/environment
/strict
/modes
/runtime
...
/framework
 
For Mono, the runtime can be instructed to forced to run an application
against a specific version of the runtime by using the --runtime
command-line option.
 
By looking at the runtime configuration section for the Mono 2.0 profile,
it's clear that the only difference between the auto and the strict mode
is exactly that additional command-line option.
 
As you can see there's no magic code involved: everything can be fully
configured in the NAnt configuration file.
 
If you have any questions or remarks regarding this new feature, just let me
know.
 
Gert
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Bug? fail/ task doesn't work as expected when calledwithin a nant.onsuccess target

2007-11-13 Thread Gert Driesen
Chris,

I'm not sure this is something we should fix. 

If we do this, then we should do it for both onsuccess and onfailure. We
then risk hiding the original build outcome.

Gert

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Lambrou
Sent: maandag 12 november 2007 16:53
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Bug? fail/ task doesn't work as expected when
calledwithin a nant.onsuccess target

Hi,

I recently posted an issue on the nant-users list, but I think the
underlying issue is one for this list. The problem is that the fail/ task
doesn't cause NAnt to terminate with a non-zero exit-code when executed from
within a target defined by the nant.onsuccess property. I think that it
should always result in a non-zero exit code (with the possible exception of
when a BuildException is explicitly caught by the trycatch task from
nant-contrib).

The scenario is that I'm using CruiseControl.NET to run a NAnt script as
part of a continuous build process. There are two conditions under which
CCNET needs to consider the build a failure:

1. Fatal errors: Typically this would be a compilation error. This is
considered fatal, as my build script cannot proceed further. In this case,
the relevant NAnt task will fail, the BuildException causes NAnt to unwind
and it terminates with a non-zero exit-code. CCNET detects this exit code,
and considers the build to have failed.

2. Non-fatal errors: This is where a condition is detected that should
result in CCNET considering the build to be a failure, but no specific task
in the NAnt script actually fails, and the script can nonetheless proceed to
completion, whereby NAnt would normally terminate with an exit code of zero.
Typically, such a compilation error might be an FxCop rule violation, or a
unit-test failure.

In the case of non-fatal error, I'm trying to force the NAnt script to fail
using the technique illustrated in the following build script (attached),
that shows three different cases:

1. Case 1: This simply illustrates NAnt running successfully.
2. Case 2: This is the typical use of the fail/ task to cause a fatal
build error.
3. Case 3: This is how I wish to deal with non-fatal errors. The case3
target modifies a property to indicate that a non-fatal error has occurred,
but script execution continues. After the rest of the script has completed,
the on-success target checks the error-message property, and tries to
fail/ the build if a non-fatal error was detected.

project name=NAnt bug xmlns=http://nant.sf.net/nant-all.xsd;

property name=error-message value=/

target name=case1
echo message=This target should result in an exit-code that
indicates success./ 
/target

target name=case2
fail message=This target should result in a exit-code that
indicates failure./
/target

target name=case3
echo message=This target should result in a exit-code that
indicates failure./
property name=error-message value=Non-fatal error./
/target

property name=nant.onsuccess value=on-success/
target name=on-success
fail message=Failure forced
if=${string::get-length(error-message)  0}/
/target
/project



The following batch script can be used to run the three different cases:

nant case1
echo Error-level: expected 0, actual %errorlevel%
nant case2
echo Error-level: expected 1, actual %errorlevel%
nant case3
echo Error-level: expected 1, actual %errorlevel%



Cases 1 and 2 work just fine. Case 3 should display this,

Error-level: expected 1, actual 1

but it actually displays this:

Error-level: expected 1, actual 0


In case 3, because NAnt terminates with an exit code of zero, CCNET assumes
that the build was successful, when in fact I want CCNET to consider the
build a failure. It's my guess that the problem isn't specific to the
fail/ task - NAnt is probably consuming any BuildException that may be
raised by the on-success task. I think that this is an error. If there's an
error in the on-success target, the build should fail, even when the main
execution of the build script was successful.


Chris

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.15.30/1125 - Release Date: 11/11/2007
21:50
 
  


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] NAnt progress

2007-10-07 Thread Gert Driesen
Hi,
 
I've decided to spend some more time on NAnt. Initial results of that work
are available in today's nightly build.
 
Some of the more visible changes since the 0.85 release are:
 
Framework support
* Added support for targeting .NET Framework 3.5
* Experimental support for targeting Silverlight / Moonlight 1.1.
* Fixed Mono support in Cygwin
 
Core
* Initial start-up time and project initialization have been reduced
dramatically.
 
Tasks
* Improvements to al, csc, vbc, ...
* Several bug fixes.
 
Types
* Case-sensitivity fixes for fileset.

Binary distributions:
http://nant.sourceforge.net/nightly/latest/nant-bin.zip
http://nant.sourceforge.net/nightly/latest/nant-bin.tar.gz
 
Source distributions:
 
http://nant.sourceforge.net/nightly/latest/nant-src.zip
http://nant.sourceforge.net/nightly/latest/nant-src.tar.gz
 
Check out the release notes for a full list of changes:
http://nant.sourceforge.net/nightly/latest/releasenotes.html
 
All feedback is appreciated!
 
Gert


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Has NAnt development ceased?

2007-09-18 Thread Gert Driesen
Jason,
 
NAnt developent has not ceased, but I haven't spend much time on it later
(except from bug fixes).
 
Release notes that list some of the changes since the 0.85 release:
http://nant.sourceforge.net/nightly/latest/releasenotes.html
 
New contributors are always welcome :-)
 
Gert
 
  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason
Grundy
Sent: dinsdag 18 september 2007 16:37
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Has NAnt development ceased?


This question is not intended to be a criticism of existing contributers. I
am simply trying to understand that status of this project?

Jason.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Nant Contributions

2007-04-09 Thread Gert Driesen
Alex,
 
Pick the area you're most interested in. What experience do you have ?
 
Gert
  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
Rovner
Sent: maandag 9 april 2007 16:47
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Nant Contributions


I would like to contribute to NAnt where can i begin?

Thanks
Alex


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt on Gump, NAnt on Mac OS/X

2007-02-17 Thread Gert Driesen


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nant-
 [EMAIL PROTECTED] On Behalf Of Curt Arnold
 Sent: zaterdag 17 februari 2007 18:59
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] NAnt on Gump, NAnt on Mac OS/X
 
 This is a continuation of a thread on general@gump.apache.org: http://
 mail-archives.apache.org/mod_mbox/gump-general/200702.mbox/%
 [EMAIL PROTECTED]
 
 
 On Feb 17, 2007, at 12:43 AM, Gert Driesen wrote:
 
 
  -Original Message-
  From: Curt Arnold [mailto:[EMAIL PROTECTED]
  Sent: zaterdag 17 februari 2007 6:20
  To: Gump code and data
  Subject: Re: Issue building NAnt
 
 
  On Feb 16, 2007, at 7:09 PM, Curt Arnold wrote:
  However, if you try to do nant or nant test, you will get a
  failure that exec doesn't support the managed attribute.  It
  appears that the build file for NAnt requires features that are not
  in NAnt 0.85.  Removing the managed=true replaces that error with
  another when it tries to run the generated nant.exe as a Mac OS/X
  executable.
 
 
 
  Changing managed=true to useruntimeengine=true will let the
 units
  test pass.  I'd suggest using the old name so that you can build the
  next release of NAnt with the current release of NAnt and make the
  switch after the next release.  Basically undo this commit: http://
  nant.cvs.sourceforge.net/nant/nant/NAnt.build?r1=1.236r2=1.237
 
  I wonder if Ant also does not require to bootstrap the version of
  Ant that
  you want to build.
 
  I don't think it's necessary to ensure NAnt can be built using a
  previous
  release, if such a bootstrap procedure is in place.
 
  Nevertheless, I have no problem undoing that commit. It's your call.
 
  Gert
 
 
 I don't know Ant's policy on this.  I think switching back to
 useruntimeengine is beneficial particular since Mono is bundled with
 0.85.

Ok, I'll do this tomorrow.

 I was trying to scramble to get something building on Mac OS/X and my
 first attempt using make failed with:
 
  BUILD FAILED
 
  The current runtime framework 'mono-2.0' is not correctly
  configured in the NAnt configuration file.
  Unable to locate 'mono' module using pkg-config. Download the
  Mono development packages from http://www.mono-
 project.com/downloads/.
 
  For more information regarding the cause of the build failure, run
  the build again in debug mode.
 
 Which stopped me cold.  Then I found that NAnt 0.85 was installed
 with Mono and then tried using NAnt 0.85 to build NAnt which lead to
 me the install bug (See http://www.bleepsoft.com/tyler/index.php?
 itemid=82 and http://bugzilla.ximian.com/show_bug.cgi?id=79671) and
 then the use of managed=true.
 
 On reflection, the make build on Mac OS/X is suffering from the same
 problem that affected the Mono install.  NAnt is unable to find the
 pkgconfig without PKG_CONFIG_PATH being explicitly set.  If I did:
 
 setenv PKG_CONFIG_PATH /Library/Frameworks/Mono.framework/Versions/
 Current/lib/pkgconfig
 
 before running make, it still failed but differently.   It might be
 helpful to mention setting PKG_CONFIG_PATH in README.txt and possibly
 change the message that is given since the prescribed remedy does not
 fix them problem.  Maybe a link to a page describing how to
 troubleshoot pkg-config problems would be better.

Ok, I'll look into this.

 After setting PKG_CONFIG_PATH, the build fails like so:
 
Buildfile: file:///Users/curta/ls-svn/nant/src/NAnt.Core/
 NAnt.Core.build
  Target framework: Mono 2.0 Profile
  Target(s) specified: build
 
 
  build:
 
[csc] Compiling 158 files to '/Users/curta/ls-svn/
 nant/build/mono-2.0.unix/nant-0.86-debug/bin/NAnt.Core.dll'.
 [resgen] Mono Resource Generator version
 0.1
 [resgen] Usage:
 [resgen]   resgen source.ext [dest.ext]
 [resgen]   resgen /compile source.ext
 [,dest.resources] [...]
 [resgen]
 [resgen] Convert a resource file from one
 format to another.
 [resgen] The currently supported formats
 are: '.txt' '.resources' '.resx' '.po'.
 [resgen] If the destination file is not
 specified, source.resources will be used.
 [resgen] The /compile option takes a list
 of .resX or .txt files to convert to
 [resgen] .resources files in one bulk
 operation, replacing .ext with .resources for
 [resgen] the output file name.
 [resgen]
 
  BUILD FAILED
 
  External Program Failed: /Library/Frameworks/
 Mono.framework/Versions/1.2.3.1/lib/mono/2.0/resgen.exe (return code
 was 1)

This should now be fixed in CVS (since earlier today). I had submitted a
patch for Mono, but it didn't get approved in time for the 1.2.3.1 release.

I've committed

[nant-dev] waitforexit

2007-02-05 Thread Gert Driesen
Hi Jay (or anyone else with an opinion on this),

Few small questions: 

I'm adding a first version of a waitforexit task to NAntContrib (which can
be used in combination with spawned processes), and wondered if that task
should fail if the process you're waiting for exits with a non-success exit
code (!= 0) ?

Should we fail if the process is no longer running. I don't so, do you ?

I think we should have a resultproperty attribute. If we do not fail the
task if the process is no longer running, then should we just not set the
property of should we assign a magic value to it ?

Gert


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] NAnt using wrong DLL - possible bug?

2006-10-30 Thread Gert Driesen
Paul,

The nunit2 task uses the NUnit API to run the tests. As a result, the unit
tests are executed in the CLR that is hosting NAnt.

I will soon add an nunit-console task that will run the nunit-console.exe
that corresponds with the target framework.

Gert

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nant-
 [EMAIL PROTECTED] On Behalf Of Paul Miles
 Sent: maandag 30 oktober 2006 16:13
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] NAnt using wrong DLL - possible bug?
 
 Hello,
 
 I have a unit test which passes when using NUnit 2.2.6 directly
 (command line or GUI) but fails when running with Nant. I believe that
 I have found a bug where NAnt uses the a version of a DLL for a
 different framework version, but I want a second opinion before
 reporting a bug.
 
 The computer has the following frameworks installed:
 * 1.0.3705
 * 1.1.4322
 * 2.0.50727
 
 The desired framework is 1.1.4322. We are using Visual Studio 2003 for
 this particular project.
 
 The Unit Test (see below) correctly throws a FileNotFoundException
 when running with NUnit directly, but throws a
 System.TypeLoadException when running the test with NAnt which causes
 the test (and subseqently the build) to fail.
 
 The Type class is located in the mscorlib.dll. Using Process Explorer
 I've discovered that NUnit is using the DLL located at:
   C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorlib.dll
 and NAnt is using the DLL located at:
   C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\mscorlib\bbfd2fbe0
 872e74abd524b4fab0a\mscorlib.ni.dll
 
 Has anyone else with multiple frameworks installed encountered this
 issue. Is there some other NAnt setting that I missed (see build file
 below) or any other recommendations? Should I report a bug?
 
 Thanks!
 
 UNIT TEST
 =
 [Test()]
 [ExpectedException( typeof( FileNotFoundException ), File or assembly
 name System, or one of its dependencies, was not found. )]
 public void Paul()
 {
   Type.GetType( System.NotAnObject, System, true );
 }
 
 
 BUILD FILE
 ==
 ?xml version=1.0 ?
 project name=InventoryDriverSolution default=test
   xmlns=http://nant.sf.net/release/0.85/nant.xsd;
 
   property name=solution.dir value=${project::get-base-
 directory()} /
   property name=nant.settings.currentframework value=net-1.1/
 
   target name=clean
   delete dir=${build.dir}/
   /target
 
   target name=build
   solution configuration=debug
   solutionfile=${solution.dir}\ClassLibrary1.sln
   outputdir=build\debug
   /solution
   /target
 
   target name=test depends=build
   nunit2 verbose=true
   formatter type=Plain/
   test assemblyname=build\debug\ClassLibrary1.dll
/
   /nunit2
   /target
 /project
 
 ---
 --
 Using Tomcat but need to do more? Need to support web services,
 security?
 Get stuff done quickly with pre-integrated technology to make your job
 easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache
 Geronimo
 http://sel.as-
 us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] aspnet_compiler task

2006-10-17 Thread Gert Driesen
Ram,

Send them to the NAnt or NAntContrib list. I cannot guarantee that I'll have 
to look into these soon.

Also, I think we should first discuss how we're going to package these .NET 
2.0 (and higher) extensions.

Gert

- Original Message - 
From: Ramprakash Gopinathan [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; 'Martin Aliger' 
[EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
Sent: Monday, October 16, 2006 10:53 PM
Subject: Re: [nant-dev] aspnet_compiler task



Gert,
I currently have one task i wrote for .NET 2.0, this is to get propery value 
from msbuild project file.  We have a 2 generic targets called fxcop and 
CodeCoverage  in master build script that has the need to examine project 
properties.
for instance the fxcop target loops through all project files in source 
directory to get assembly name and uses it to run fxcop.
Do you want me to send the source files with tests to you? I can add the 
aspnet_compiler tasks to this list as well

Let me know...

Thanks,
Ram/


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; 
[EMAIL PROTECTED]; [EMAIL PROTECTED]: RE: 
[nant-dev] aspnet_compiler taskDate: Mon, 16 Oct 2006 19:08:58 +0200






Hi Martin, Ram,

Nothing prevents us from having a separate NAnt.Contrib assembly for 2.0 
specific extensions (tasks, functions, filters, …).

We could also conditionally build these extension when NantContrib is built 
targeting .NET 2.0, but then the official binary distribution would not 
contain these extensions.

Gert




From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
Ramprakash GopinathanSent: maandag 16 oktober 2006 18:44To: Martin Aliger; 
[EMAIL PROTECTED]: Re: [nant-dev] aspnet_compiler 
task

Hi Martin, I din't realize that contrib tasks need to be compatible under 
1.0, I guess I'll add it to my custom tasks list for 2.0. I suggested it 
because its going to be a common task that everyone who is trying to 
automate asp.net builds is going to want it. May be we need a nant20 contrib 
site we can post all tasks 2.0 specific stuffThanks for clarifying it Ram/



 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; 
 nant-developers@lists.sourceforge.net Subject: RE: [nant-dev] 
 aspnet_compiler task Date: Mon, 16 Oct 2006 18:22:26 +0200  Hi Ram,  
 I'd love to see such a task, even more if it supports WebApplication 
 model (as well as web sites). Also there is aspnet_merge tool, which 
 would be very nice to have (they are interconnected afaik).  btw: those 
 functionalities could be accessed directly via System.Web.Compilation 
 namespace. Or perhaps as commandline wrappers. I'd like more the direct 
 calls, even that it will need 2.0 framework (which is problem in current 
 contrib project). But you can always make new Ram.NAnt.AspnetTasks.dll 
 :-) For being part of NantContrib, you'd have to be compilable under 1.0 
 though.  Martin    From: 
 [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Ramprakash Gopinathan Sent: Monday, October 16, 2006 5:52 PM To: 
 nant-developers@lists.sourceforge.net Subject: [nant-dev] aspnet_compiler 
 taskIs there any plan for adding an aspnet_compiler task to nant 
 contrib? I'd like to develop this if no one is working on it or has 
 already got something developed. Let me know what you guys think...  
 Thanks, Ram/  





 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job 
 easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642





 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] aspnet_compiler task

2006-10-16 Thread Gert Driesen








Hi Martin, Ram,



Nothing prevents us from having a separate NAnt.Contrib assembly
for 2.0 specific extensions (tasks, functions, filters, ).



We could also conditionally build these extension when NantContrib
is built targeting .NET 2.0, but then the official binary distribution would
not contain these extensions.



Gert









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ramprakash
Gopinathan
Sent: maandag 16 oktober 2006 18:44
To: Martin Aliger; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] aspnet_compiler task








Hi Martin,

I din't realize that contrib tasks need to be compatible under 1.0, I guess
I'll add it to my custom tasks list for 2.0. I suggested it because its going
to be a common task that everyonewho is trying to automateasp.net
builds isgoing to want it.

May be we need a nant20 contrib site we can post all tasks 2.0 specific stuff

Thanks for clarifying it

Ram/










 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
 Subject: RE: [nant-dev] aspnet_compiler task
 Date: Mon, 16 Oct 2006 18:22:26 +0200
 
 Hi Ram,
 
 I'd love to see such a task, even more if it supports WebApplication model
 (as well as web sites). Also there is aspnet_merge tool, which would be
very
 nice to have (they are interconnected afaik).
 
 btw: those functionalities could be accessed directly via
 System.Web.Compilation namespace. Or perhaps as commandline wrappers. I'd
 like more the direct calls, even that it will need 2.0 framework (which is
 problem in current contrib project). But you can always make new
 Ram.NAnt.AspnetTasks.dll :-) For being part of NantContrib, you'd have to
be
 compilable under 1.0 though.
 
 Martin 
 
 
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Ramprakash Gopinathan
 Sent: Monday, October 16, 2006 5:52 PM
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] aspnet_compiler task
 
 
 
 Is there any plan for adding an aspnet_compiler task to nant
 contrib? I'd like to develop this if no one is working on it or has
already
 got something developed.
 Let me know what you guys think...
 
 Thanks,
 Ram/
 
 
 








-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] NAnt 0.85 is released

2006-10-15 Thread Gert Driesen
Announcing NAnt 0.85.

Binary and source distributions are available for immediate download from:
http://sourceforge.net/project/showfiles.php?group_id=31650

About NAnt:
NAnt is a free .NET build tool, allowing applications to be built targeting
both Microsoft .NET and Mono while supporting both Windows and Linux
platforms.

Release notes and a user manual are available here:
http://nant.sourceforge.net/release/0.85/
Discussion of NAnt occurs on the mailing list at
[EMAIL PROTECTED]
Bugs can be reported using the Bug Tracker at
http://sourceforge.net/projects/nant. 

Check the NAnt homepage for additional info at http://nant.sourceforge.net.

Enjoy !

Gert


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Csc Task Ignoring References

2006-10-12 Thread Gert Driesen

- Original Message - 
From: Ryan Baxter [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: nant-developers@lists.sourceforge.net
Sent: Thursday, October 12, 2006 7:36 PM
Subject: Re: [nant-dev] Csc Task Ignoring References


 So is it that the csc compiler will ignore a /reference or /lib that it
 cannot find?  Its interesting that I can compile this project from the
 command-line using the same /reference and /lib arguments as my build 
 file.
 I began to think that somehow my {libraries.path} variable wasn't being 
 set
 property so I hardcoded the direct path in my lib section, but still had
 the same compile errors.  Confused.  Thanks for the response.

With csc I meant the csc task, not the csc compiler.

 On 10/12/06, Gert Driesen [EMAIL PROTECTED] wrote:

 Ryan,

 In that case, csc cannot locate the referenced assemblies.

 Gert
 - Original Message -
 From: Ryan Baxter [EMAIL PROTECTED]
 To: nant-developers@lists.sourceforge.net
 Sent: Thursday, October 12, 2006 5:57 PM
 Subject: [nant-dev] Csc Task Ignoring References


 I have a build script that looks something like the following:
 
  target name=compile description=Compile the source code.
 echo message=Building assembly ${project.name}. /
 csc target=library keyfile=${project.name}.snk output=${
  output.path}/${project.name}.dll debug=${build.debug} 
  verbose=true
   sources
 include name=**/*.cs /
   /sources
   references
 lib
   include name={libraries.path}\some\path /
   include name={libraries.path}\other\path /
 /lib
 include name=Some.dll /
 include name=Other.dll /
   /references
 /csc
   /target
 
  When calling this target from NAnt, I get a type or namespace could not
 be
  found compilation error with the verbose output looking something like
 the
  following:
 
  [csc] Output file 'D:\TeamDevelopment\BuildArea\Output\Project
  1.0\Project.Website\Project.Website.dll' does not exist, rebuilding.
  [csc] Compiling 9 files to 'D:\TeamDevelopment\BuildArea\Output\Project
  1.0\Project.Website\Project.Website.dll'.
  [csc] Contents of C:\Documents and Settings\genzweb\Local
  Settings\Temp\tmp23E6.tmp.
  [csc] /fullpaths /debug /define:DEBUG /define:TRACE /nologo
  /target:library /out:D:\TeamDevelopment\BuildArea\Output\Project
  1.0\Project.Website\Project.Website.dll
  /keyfile:D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Project.Website.snk
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Bdp\Form1.aspx.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Bdp\Form1.aspx.designer.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\DatePicker\DatePicker.aspx.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Properties\AssemblyInfo.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Properties\VersionInfo.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Tmf\Form1.aspx.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Tmf\Form1.aspx.designer.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Default.aspx.cs
  D:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Default.aspx.designer.cs
  [csc] Starting 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\csc.exe
  (@C:\Documents and Settings\genzweb\Local Settings\Temp\tmp23E6.tmp)'
 in
  'D:\TeamDevelopment\BuildArea\Source\Project 1.0\Project.Website'
  [csc] d:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Bdp\Form1.aspx.cs(18,7): error CS0246: The type or
  namespace name 'Some' could not be found (are you missing a using
  directive
  or an assembly reference?)
  [csc] d:\TeamDevelopment\BuildArea\Source\Project
  1.0\Project.Website\Bdp\Form1.aspx.designer.cs(15,19): error CS0246: 
  The
  type or namespace name 'Other' could not be found (are you missing a
 using
  directive or an assembly reference?)
 
  It appears almost as if my references aren't being included as
 parameters
  of
  the csc.exe call.  I have other projects that use similar methods for
  compiling without problems.  I've checked my working source directory
 and
  the build files do include the correct references.  Ideas?  Thanks in
  advance.
 



 


 
 -
  Using Tomcat but need to do more? Need to support web services,
 security?
  Get stuff done quickly with pre-integrated technology to make your job
  easier
  Download IBM WebSphere Application Server v.1.0.1 based on Apache
 Geronimo
  http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642



 


  ___
  nant-developers mailing list
  nant-developers

Re: [nant-dev] Building VS2005 projects using NANT 8.5 rc4

2006-10-11 Thread Gert Driesen








No, this will only be supported after the 0.85 release. We do
support.NET 2.0, but not (yet) VS 2005 solutions and project.



Gert









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ramprakash
Gopinathan
Sent: woensdag 11 oktober 2006 18:33
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Building VS2005 projects using NANT 8.5 rc4








Is building vs2005 projects supported? Document says framework 2.0 is
supported.
I'm getting a project guid not found error when i build my vs2005 project using
nant 8.5 rc4

Thanks,
Ram/








-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Problem in add reference of the other project inSolution

2006-09-18 Thread Gert Driesen
Amish,

Do you have a self-contained repro you can share for this issue ?

Gert

- Original Message - 
From: amish [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Monday, September 18, 2006 9:19 AM
Subject: [nant-dev] Problem in add reference of the other project 
inSolution


 Hi
 I am new to NANT.
 I have two projects in my solution file .

 SOLTUIN FILE
  |
 + PROJECT A ( WEB BASED PROJECT)
  |
  |_ BIN
   |_ Project B's Assembly reference
  |
  |_PROJECT B (windows based)

 My PROJECT B  contains many dll file refernces .
 so when my build starts it first start build PROJECT B and then
 PROJECT A. Now after PROJECT B  build gets compelted and as soon as it
 start PROJECT A then it gives an error saying that

 Cannot copy 
 'd:\cvtproton\BIREPORTSDLL\bin\Release\CrystalDecisions.ReportAppServer.ReportDefModel.dll'
 to 'd:\cvtproton\bin\CrystalDecisions.ReportAppServer.ReportDefModel.dll'.
The process cannot access the file
 'd:\cvtproton\bin\CrystalDecisions.ReportAppServer.ReportDefModel.dll'
 because it is being used by another process.

 This error occurs while copying PROJECT B/BIN/DLL File to PROJECT A/BIN

 These error not only occurs for one partucular dll (i.e
 CrystalDecisions.ReportAppServer.ReportDefModel.dl ) but any other dll
 has in
 PROJECT B/BIN/ folder.


 It would be great if some one can help me out.

 Thanks
 Amish H Khatri






 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job 
 easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642





 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Error CS1703 when using NAnt task...

2006-09-13 Thread Gert Driesen
John,

This appears to be due to some change in .NET 2.0 wrt to the assembly
loader.

I'll commit a workaround to cvs in a minute.

Gert

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nant-
 [EMAIL PROTECTED] On Behalf Of John Cole
 Sent: woensdag 13 september 2006 17:24
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Error CS1703 when using NAnt task...
 
 I was able to make a new MSI and started testing against our build
 scripts (YEA!).
 
 I've run into a problem.  If I execute the nant task on a build files
 that have a script tags that loads the same assembly, I get the
 following
 error:
 
 C:\src\NAnt\UtilityCenter\2x\uai\Utilities\PerformanceCalculator\defaul
 t.bui
 ld(149,3):
 Compilation failed:
 error CS1703: An assembly with the same identity
 'System.Data, Version=2.0.0.0, Culture=neutral,
 PublicKeyToken=b77a5c561934e089' has already been imported. Try
 removing one of the duplicate references.
 
 If you want to simulate this, create two build files and place the
 following script in each one:
 
   script language=C# prefix=script
   references
   include name=System.Data.dll /
   /references
 
   code![CDATA[
 
   [Function(CreateRegistryGuid)]
   public string CreateRegistryGuid() {
 
   return { + Guid.NewGuid().ToString().ToUpper() +
 };
 
   }
 
   ]]
   /code
   /script
 
 
 Now create a build file that calls both of those via a nant task.
 The second call should fail.
 
 Thanks,
 
 John
 This email and any files transmitted with it are confidential and
 intended solely for the use of the individual or entity to whom they
 are addressed. If you have received this email in error please notify
 the sender. This message contains confidential information and is
 intended only for the individual named. If you are not the named
 addressee you should not disseminate, distribute or copy this e-mail.
 
 ---
 --
 Using Tomcat but need to do more? Need to support web services,
 security?
 Get stuff done quickly with pre-integrated technology to make your job
 easier Download IBM WebSphere Application Server v.1.0.1 based on
 Apache Geronimo
 http://sel.as-
 us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Upgrade ziplib to 0.84?

2006-08-18 Thread Gert Driesen


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nant-
 [EMAIL PROTECTED] On Behalf Of Toby Johnson
 Sent: vrijdag 18 augustus 2006 16:24
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Upgrade ziplib to 0.84?
 
 Are there any plans to upgrade to the latest ziplib library (0.84) with
 the next Nant release? I see it's been at 0.83 for a while, and that
 version has a bug which prevents it from unzipping archives which
 contain zero-byte files (one of which happens to be the Subversion
 releases).
 
 http://wiki.sharpdevelop.net/default.aspx/SharpZipLib.ReleaseHistory

We already use #ziplib 0.84, however that version does not fix the issue
with unzipped of zero-length files:

http://community.sharpdevelop.net/forums/thread/10051.aspx

However, recent nightly builds of NAnt contain a workaround for that issue.

Gert


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VSWebCache ObjectDir solution

2006-08-03 Thread Gert Driesen

- Original Message - 
From: Martin Aliger [EMAIL PROTECTED]
To: 'mike61079' [EMAIL PROTECTED]; 
nant-developers@lists.sourceforge.net
Sent: Thursday, August 03, 2006 10:07 AM
Subject: Re: [nant-dev] VSWebCache ObjectDir solution


 I have the same setup as you, everything is in distinct
 directories and then it ends up sharing VSWebCache because
 the project names are the same.

 First - bad documentation! If there was any mention of VSWebCache, I'd try
 to prepare for this. I was not aware of any (shared) cache up to problems!

This is what's so great about open-source development: you can now correct 
the docs yourself ;-)

 I thought VS also built files in a local obj directory? I
 know for DLL's it does that. Is there a way to use that with
 web projects?

 I just checked that - and yes, it seems VS _is using_ obj folder for
 WebProject as well! Atleast, I have obj folder in the project. Perhaps VS 
 is
 writing both - VSWebCache _and_ obj folder ?

Hmm, I'll look into this asap.

Gert 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VSWebCache ObjectDir solution

2006-08-02 Thread Gert Driesen

- Original Message - 
From: Martin Aliger [EMAIL PROTECTED]
To: 'Gert Driesen' [EMAIL PROTECTED]; 'mike61079' 
[EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
Sent: Wednesday, August 02, 2006 11:16 AM
Subject: RE: [nant-dev] VSWebCache ObjectDir solution


 But I'm not sure, if using _any_ cache is good thing.

 I understand, but we should remain compatible with VS where
 possible and in this case it's even necessary (for creating
 strong named assemblies).

 Could you clarify that strong name thing, please?
 VS compatibility is a good thing, but I don't see it as necessarity in my
 case. We have extra features in solution, and maybe ability turning off
 something VS does, is not so bad as well. Anyway, we need strong names
 support in any case, that's sure.

For csc to be able to resolve the relative path specified in AssemlyKeyFile 
in the same way as Visual Studio, we need to store our intermediate build 
output in the same folder structure.

  I want to do CLEAN build, so I delete all output files, all obj
  folder and still - there is hidden cache! Even
 non-documented cache. I
  don't see this as the right way...

  For this, I've been meaning to introduce a clean mode for
 the solution task, but I haven't yet found time for it (pf).

 No problem - we are all busy :-)

 No interim files is not an option: this would result in very
 bad performance for embedded resources as they would have to
 be recompiled on every run.

 Yes - it is. But sometimes it's not a problem. I do not mind if nighly 
 build
 takes 2 hours instead of 1 at all. I usually sleep in that time anyway :-)

Would a clean mode help you sleep better, or do you want to get rid of the 
VSWebCache for another reason (eg. for parellel builds, although you'll have 
this problem too with local obj dirs) ?

  btw: could be solution compiled completely without obj folders? I
  think some very old NAnt do not used them (0.84?) Or
 alternativelly -
  could we use one folder (say c:\temp) for obj folders of
 all projects
  in the solution?

 No, we must use the same folder structure as Visual Studio.
 If not, we run into problems with relative paths (in the
 AssemblyKeyFile assembly-level attribute).

 Is this totally needed? Say - other than AssemblyKeyFile relative path 
 will
 broke? This could be documented behaviour of such an attribute
 (interim-path)

Ofcourse, but I'm afraid such an attribute might introduce more issues than 
it will solve.

Same thing goes for the outputdir attribute that we have already. If it were 
up to me, we'd lose support for it immediately.

solution task is there for compatibility with Visual Studio, if users want 
total control then they should use the individual compiler tasks.

 Also, a temp directory should only be used for temporary
 files, and intermediate build output cannot be considered temp files.

 Yes - temp was bad example.
 In fact, obj folders are not so bad. They are local to sourcecode, one is
 used to them from VS etc. But VSWebCache is bad in my eyes. That is
 something like static variable in multithreaded application. You never 
 know,
 when and what it broke.

I agree, but I'd hate introducing a new attribute for each indivual usage 
scenario.

Gert 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VSWebCache ObjectDir solution

2006-08-02 Thread Gert Driesen

- Original Message - 
From: Martin Aliger [EMAIL PROTECTED]
To: 'Gert Driesen' [EMAIL PROTECTED]; 'mike61079' 
[EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
Sent: Wednesday, August 02, 2006 12:50 PM
Subject: Re: [nant-dev] VSWebCache ObjectDir solution


 Would a clean mode help you sleep better, or do you want to
 get rid of the
 VSWebCache for another reason (eg. for parellel builds,
 although you'll have
 this problem too with local obj dirs) ?

 The parallel builds nighmares me. obj dirs are ok, I think. They should 
 not
 cause any trouble.
 clean build is another issue, not so high on my priorities. Maybe it 
 could
 simply delete all obj dirs/output dir before build? It is basically what 
 VS
 do, isn't it?

 Same thing goes for the outputdir attribute that we have
 already. If it were
 up to me, we'd lose support for it immediately.

 Oh - I strictly disagree here. I, personally, use solution task _becouse
 of_ thouse additional stuff. Unless them, you could exec devenv.exe with
 /rebuild and you have it. Ok - there is mono support, licence issues, etc.
 But outputdir is one of so important features!

No problem. We'll never remove support for it, but personally I don't think 
it's very useful.

Another important feature of the solution task is that it allows you to 
target different CLR versions.

 btw: MS comes with (working) outputdir support in VS2005 as well.

   used to them from VS etc. But VSWebCache is bad in my eyes. That is
  something like static variable in multithreaded
 application. You never
  know,
  when and what it broke.

 I agree, but I'd hate introducing a new attribute for each
 indivual usage
 scenario.

 Agreed.

 First, I'll try to locally change source to rip off VSWebCache. I believe
 this is core of those problems, but lets prove it. Next, we could add
 attribute or whatever to solve those problems.

Changing to a local store for intermediate build output will not resolve 
issues if you build a project in parallel from the same local project 
directory, but I'm sure that's not what you're doing.

Just checking: should this issue postpone the 0.85 release ?  Can you submit 
a bug report for it ?

Gert 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VSWebCache ObjectDir solution

2006-08-01 Thread Gert Driesen


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nant-
 [EMAIL PROTECTED] On Behalf Of mike61079
 Sent: maandag 31 juli 2006 22:13
 To: nant-developers@lists.sourceforge.net
 Subject: Re: [nant-dev] VSWebCache ObjectDir solution
 
 
 Actually this just happened to me. I compiled the same project except
 one for dev and one for test and the debug files clashed in VSWebCache.
 Is there a way around this?

Currently, no. Did you compile both configurations in parallel ?

I'm still not sure how we should tackle this issue.

Gert


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VSWebCache ObjectDir solution

2006-07-27 Thread Gert Driesen
Martin,

We needed this to mimic the behavior of Visual Studio for web projects.

Visual Studio first writes the compiler output to that directory, and as
such the path specified in AssemblyKeyFile is resolved relative to that
directory.

Gert 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: donderdag 27 juli 2006 16:52
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] VSWebCache ObjectDir solution
 Importance: High
 
 Hello,
  
 what for is VSWebCache used in the ObjectDir (solution task) ?
  
 Could it somehow affect when 2 nants are running 
 _simultaniously_ compiling another version (branch) of the 
 same (web)project?
  
  
  
 Maybe I'm just on wrong track, but this matter seems very 
 important. Running multiple nant instances in the same time 
 is quite common on CI (main use of nant in my eyes). If this 
 is not safe... I do not like to even think about it.
  
 Martin
 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Release 0.85 and beyond

2006-07-14 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: vrijdag 14 juli 2006 12:59
 To: 'Gary Feldman'; nant-developers@lists.sourceforge.net
 Subject: Re: [nant-dev] Release 0.85 and beyond
 
 Hello,
 
 agreed - 1.0 soon is a good thing. I see only one big thing 
 which we should
 addess in 1.0: VS2005 projects. Or MSBuild cooperation. The 
 same thing.
 
 Since many developers are migrating (or already using) 
 framework 2.0 in
 VS2005 and we (currently) do not provide direct tools for 
 projects it uses,
 they could either: use plain msbuild (deserters!) or use core
 tasks-csc,regasm etc (and maintain both .csproj and .build) 
 or (as most of
 them do today) exec msbuild.exe to their .csproj file (and 
 give up project
 dependancy resolution and other solution features)

Are people really waiting for this ?

Shouldn't we focus on improving NAnt ?

 As I see it, we could:
 1/ state, that new project files used on VS2005 are unsupported
 2/ write new task which handles it somehow (aka msbuild-solution or
 new-vs2005-solution)
 3/ merge required code into current solution task

We already have an msbuild task in NAntContrib.

 Since msbuild code need to run under 2.0 framework, and NAnt 
 itself should
 run on 1.0/1.1 as well, integration (if 3 will be chosen) 
 have to be done
 carefully. Or could we restrict NAnt to 2.0 framework? I 
 don't thing so...

We could ofcourse use reflection to invoke the MSBuild API's. 

We briefly discussed this once, no ?

 Maybe 2 distributions: 1.0 compatible, and 2.0, compiled for 
 2.0 and with
 additional features?

This might create too much confusion for (some) users, no ?

Gert



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Nant contributions or where nant is going?

2006-07-02 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Flex
 Sent: donderdag 29 juni 2006 11:50
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Nant contributions or where nant is going?
 
 Guys, I'm completely newbie both to nant and to the mailing lists. I 
 enjoy nant much and have converted big project to use it and 
 plan to do 
 such with every other. However there is something that 
 disturbs me - the 
 future of nant. I have read the archives and came to several 
 conclusions:
 - newsgroups are pretty much dead

Myself and other members of the NAnt community still help people out
whenever possible.

However, I agree that the responsiveness could indeed be better.

 - nant developers are very busy and  progress is slow

We definitely have a lack of contributors. With this I'm not talking about
people that post new tasks, but we need developers  designers for improving
the NAnt core.

 - the people above does not accept contributions (?)

We definitely do (but again, our responsiness could be better).

 - nant-contrib should be the way to go but not much 
 responsiveness there too

The NAnt team decided quite a while ago that new tasks should first be added
the NAntContrib project to allow these tasks to become more mature.

 Correct me if I'm wrong, but nant core is okay, now it has 
 to only get 
 rich in tasks and become the ultimate make system you can do 
 everything 
 you can imagine with? Or nant is heading other way?

NAnt core is indeed pretty stable, but it could always do with some
performance improvements.

 My primary concern is about the contributions. Nant can move 
 pretty fast 
 forward if the people actually using it are allowed to take 
 part. Not to 
 throw the project in the wild where everyone does whatever he 
 likes with 
 it, but controlled contributions of new tasks and task enchantments 
 with voting and open discussion before. Currently, the tons of 
 deprecated task attributes shows the planning is a weak side.
 
 Opinions or I'm gonna be hanged? ;)

You're definitely not gonna get hanged. We welcome all feedback!

Are you volunteering to become part of the NAntContrib team ?

If you are, first start by submitting patches to the NAntContrib developer
list for review. If your patches meet our quality level, we'll make you a
member of the project.

After that, you can dive into the NAnt codebase.

What do you think ?

Gert



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] NAnt 0.85 Release Candidate 4 is available

2006-06-02 Thread Gert Driesen
Announcing NAnt 0.85 Release Candidate 4.

Binary and source distributions are available for immediate download from:

http://sourceforge.net/project/showfiles.php?group_id=31650

About NAnt: NAnt is a free .NET build tool, allowing applications to be
built targeting both Microsoft .NET and Mono while supporting both Windows
and Linux platforms.

Release notes and a user manual are available here:

http://nant.sourceforge.net/release/0.85-rc4/

Discussion of NAnt occurs on the mailing list at
[EMAIL PROTECTED]
Bugs can be reported using the Bug Tracker at
http://sourceforge.net/projects/nant.

Check the NAnt homepage for additional info at http://nant.sourceforge.net.

Enjoy!

Gert



___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Bug tracking status

2006-05-16 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Gary Feldman
 Sent: dinsdag 16 mei 2006 17:32
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Bug tracking status
 
 There are currently no open P9 bugs.  Only two bugs were submitted in
 the first half of May, nine in all of April.  Of the nine in 
 April, two
 were duplicates, one had already been fixed, one was user 
 error, one has
 been fixed, two are pending more information.  I've marked one of them
 postponed, because I don't believe it's needed for 0.85.  Only one of
 the two May bugs looks like it needs to be addressed (1481841 exec
 task's commandline and arg eat = signs
 https://sourceforge.net/tracker/index.php?func=detailaid=148
 1841group_id=31650atid=402868 
 
 ), but I suspect that arg value... can be made to work.

Gary, were you able to reproduce this issue ? It's working fine here.

I think that the issue described by the submitter is due to the way command
line arguments for batch files are processed, and as such this has nothing
to do with NAnt itself.

 In my opinion, that's enough to close out 0.85 and release 
 it.  Granted,
 I'm exploiting the fact that the default priority is 5, not 9.
 Nevertheless, 0.85 is still a pre-1.0 version number and there's more
 noise about getting a new release out than fixing any particular bug.
 Furthermore, a release is really necessary at this time to maintain
 credibility against MSbuild.
 
 Therefore, I propose that the next full build be declared the 
 0.85 final
 release, and that 0.86 be opened.  The only exception to this would be
 any identified showstoppers, where showstopper is defined as:  a) it
 affects most NAnt users; b) there is no workaround; and either c1) it
 prevents using NAnt for its primary purpose (building .Net 
 projects) or
 c2) the fix would break many existing build files.  I can even be
 convinced to remove c2, but I doubt that's an issue.

I'd still prefer to have one more release candidate before we ship a new
final release.

I hope to have time in the next two weeks, but I realise I've said that
before :(

We've also lost the instructions for our release procedure when the Wiki was
killed (pfff), so it'll take a little longer than usually.

Gert



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] $(ENV_VAR) references in project-file RelativePath attribute

2006-04-23 Thread Gert Driesen
Harmon,

Expansion of environment variables in path should not be part done in
FileUtils, as this is not something that should to be done for all paths.

The modifications should be limited to the solution task's support for C++
(meaning src\NAnt.VSNet\Vc*.cs).

Can you also make that patch against NAnt cvs (or a recent nightly build),
and also create a small repro for this issue ?

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Harmon Nine
 Sent: donderdag 13 april 2006 18:33
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] $(ENV_VAR) references in project-file 
 RelativePath attribute
 
 Hello all.
 
  
 
 I'm currently trying to use NAnt as an automated build tool 
 for a project here at Vanderbilt.  The code is in C++ and is 
 modified through Visual Studio 7.1.
 
  
 
 We are using the NAnt solution task in the NAnt build file. 
  A problem occurs using the NAnt solution task under the 
 following circumstances:
 
  
 
 Some of the source files (e.g. *.cpp files) in the project 
 are not within the project directory structure.  Rather, they 
 are part of a separate package that must already be installed 
 in order to perform the project build.  The location of the 
 package is indicated by an environment variable called 
 PKG_ROOT, which is set to C:\Path_To_Package.
 
  
 
 To include a source file from the this package in the 
 project, i.e. so that it will be compiled as part of the 
 project, the file's Relative Path, as set in the file 
 properties window of VS, is 
 $(PKG_ROOT)\path_to_file_from_PKG_ROOT.  In the .vcproj 
 file, this value shows up in the RelativePath attribute of 
 a File element.
 
  
 
 Note the syntax of the environment variable reference, i.e. 
 $(ENV_VAR).  This syntax is used elsewhere in VS, e.g. in the 
 Tools-Options-Projects-Directories window for specifying 
 various pertinent directories (e.g. include directories).
 
  
 
 Unfortunately, when this RelativePath is expanded by NAnt, it 
 becomes 
 C:\Build_Directory\$(PKG_ROOT)\path_to_file_from_PKG_ROOT, 
 which (obviously) causes the build to fail.
 
  
 
  
 
 The build in VS works fine, leading me to believe that VS:
 
  
 
 1. Expands environment variable references ( like $(ENV_VAR) 
 ) in the RelativePath attribute before it uses this attribute.
 
 2. When VS notices that the value of the RelativePath 
 attribute is actually an absolute path (e.g. it starts with 
 C:\), it does not prepend the project directory path onto it.
 
  
 
  
 
 I made a modification to the NAnt code to implement this 
 functionality.  The diff file is included as an attachment. 
  There may be a better means of implementing this, but 
 regardless, it would be nice to have this functionality in 
 the final 0.85 release.
 
  
 
 Thanks.
 
 -- Harmon
 
 



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] VSSGet via NAnt.Contrib.Tasks

2006-04-23 Thread Gert Driesen
Righardt,

This is now fixed in cvs, and the fix will be part of the next nightly build
or release. 

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Marais Righardt
 Sent: woensdag 12 april 2006 11:09
 To: 'nant-developers@lists.sourceforge.net'
 Cc: '[EMAIL PROTECTED]'
 Subject: [nant-dev] VSSGet via NAnt.Contrib.Tasks
 
 Hi I am getting this error message when I try to get latest 
 from VSS of a specific file. 
 
 ~~~ 
 NAnt 0.85 (Build 0.85.1932.0; rc3; 16/04/2005) 
 Copyright (C) 2001-2005 Gerry Shaw 
 http://nant.sourceforge.net 
 
 Buildfile: file:///C:/Projects/VSSGetScripts/get_build_files.build 
 Target framework: Microsoft .NET Framework 1.1 
 
 [loadtasks] Scanning assembly NAnt.Contrib.Tasks for extensions. 
[vssget] Getting '$/Projects/ISAS/Source Code/App 
 Server/AppServer.build' to 
 'C:\Projects\ISAS\Source Code\App Server'... 
[vssget] Removing deleted files from local image... 
 
 BUILD FAILED 
 
 INTERNAL ERROR 
 
 System.Runtime.InteropServices.COMException (0x80042979): 
 This command only work 
 s on projects. 
at SourceSafeTypeLib.VSSItemClass.get_Items(Boolean 
 IncludeDeleted) 
at 
 NAnt.Contrib.Tasks.SourceSafe.GetTask.RemoveDeletedFromLocalIm
 age(IVSSItem 
  item, String localPathPrefix) 
at 
 NAnt.Contrib.Tasks.SourceSafe.GetTask.RemoveDeletedFromLocalImage() 
at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask() 
at NAnt.Core.Task.Execute() 
at NAnt.Core.Project.InitializeProjectDocument(XmlDocument doc) 
at NAnt.Core.Project.Execute() 
at NAnt.Core.Project.Run() 
 
 Please send bug report to [EMAIL PROTECTED] 
 ~~~ 
 
 The script looks like this. 
 
 ?xml version=1.0? 
 project name=release value=Release 
 
 !-- Local path to the Release folder -- 
 property name=release.root value=C:\Projects / 
 !-- root build folder -- 
 
 !-- Visual Source-Safe -- 
 property name=vss.username value=builder / !-- 
 vss user name. -- 
 property name=vss.password value=builder / !-- 
 password for vss user name -- 
 property name=vss.database 
 value=C:\Temp\VSS_CCNET\srcsafe.ini / !-- path to the vss 
 db. user executing this build needs rights to this path --
 
 property name=vss.release.root value=$/Projects 
 / !-- root release location -- 
 property name=vss.checkoutBin value=false / 
 !-- default value for vss checkuout -- 
 
 !-- Load the NANTCONTRIB assembly for use with NAnt 
 --
 loadtasks 
 assembly=${path::combine(environment::get-variable('NANTCONTR
 IB_DIR'), 'bin/NAnt.Contrib.Tasks.dll')} /
 
 
 !-- Get latest of the build files -- 
 !-- Get latest of the Application server build files -- 
 vssget username=${vss.username} 
 password=${vss.password} 
 localpath=${release.root}\ISAS\Source Code\App Server 
 recursive=true removedeleted=true replace=true 
 writable=false dbpath=${vss.database} 
 path=${vss.release.root}/ISAS/Source Code/App 
 Server/AppServer.build /
 
 /project 
 
 ~~~ 
 
 thanks 
 
 Righardt Marais 
 Cellular - +27 (0) 82 444 7577
 Email - [EMAIL PROTECTED] 
 
 Please click on the following link to read the Old Mutual 
 legal notice: 
 http://www.oldmutual.co.za/e-mail_legal_notice 
 Alternatively, send a blank e-mail to 
 mailto:[EMAIL PROTECTED] 
 
  
 
 



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Internal error: illegal characters in exec call

2006-04-23 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Trevor Misfeldt
 Sent: maandag 27 maart 2006 6:01
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Internal error: illegal characters in exec call
 
 
 I got this error with this line:
 
 exec program=csc /t:library /platform:x86
 /addmodule:../Shared/NMathShared.netmodule
 /addmodule:../Kernel/NMathKernel.netmodule /out:NMathCore.dll *.cs/
 
 The execution works fine from the command-line. Should I be escaping
 characters there? 

You should use arg element to specify the commandline argument for csc:

exec program=csc
arg value=/t:library /
arg value=/platform:x86 /
...
/exec

 BTW, I'm doing this 'cause I don't see a platform option on 
 csc yet. I'm
 using a nightly build from a few days ago.

I'll add this asap.

Gert



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Error on using NAnt

2006-04-23 Thread Gert Driesen
Sanjiv,

There have been reports of similar issues in the past, and these were always
caused by a bad install of the .NET Framework.

Can you trying reinstalling the .NET Framework 1.1 redistributable?

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Sanjiv
 Sent: donderdag 23 maart 2006 7:44
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Error on using NAnt
 
 Hi Developers,
  
 I am using NANT to build my project solution. This solution 
 file contains multiple projects developed in C++, WTL, C#, VB.NET
 It is giving me following error.
 --
 --
 C:\Program Files\nant-0.85-rc3\binNAnt build 
 -buildfile:I:\ProjectFolder\ATS\VDO.build
 NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005)
 Copyright (C) 2001-2005 Gerry Shaw
 http://nant.sourceforge.net http://nant.sourceforge.net/ 
  
 Buildfile: file:///I:/Snap-On/ATS/VDO.build
 Target framework: Microsoft .NET Framework 1.1
 Target(s) specified: build
  
 
 build:
  
 
 build.VDO:
  
  [solution] Starting solution build.
  
 BUILD FAILED
  
 INTERNAL ERROR
  
 System.TypeInitializationException: The type initializer for 
 NAnt.DotNet.Tasks.
 CompilerBase threw an exception. --- 
 System.ArgumentException: Culture ID 3177
 0 (0x7C1A) is not a supported culture.
 Parameter name: culture
at System.Globalization.CultureInfo..ctor(Int32 culture, 
 Boolean useUserOverr
 ide)
at 
 System.Globalization.CultureTable.GetCultures(CultureTypes types)
at System.Globalization.CultureInfo.GetCultures(CultureTypes types)
at NAnt.DotNet.Tasks.CompilerBase..cctor()
--- End of inner exception stack trace ---
at 
 NAnt.DotNet.Tasks.CompilerBase.GetResourceCulture(String 
 resourceFile, Str
 ing dependentFile)
at NAnt.VSNet.Resource..ctor(ManagedProjectBase project, 
 FileInfo resourceSou
 rceFile, String resourceSourceFileRelativePath, String 
 dependentFile, SolutionTa
 sk solutionTask, GacCache gacCache)
at NAnt.VSNet.ManagedProjectBase..ctor(SolutionBase 
 solution, String projectP
 ath, XmlElement xmlDefinition, SolutionTask solutionTask, 
 TempFileCollection tfc
 , GacCache gacCache, ReferencesResolver refResolver, 
 DirectoryInfo outputDir)
at NAnt.VSNet.VBProject..ctor(SolutionBase solution, 
 String projectPath, XmlE
 lement xmlDefinition, SolutionTask solutionTask, 
 TempFileCollection tfc, GacCach
 e gacCache, ReferencesResolver refResolver, DirectoryInfo outputDir)
at NAnt.VSNet.ProjectFactory.CreateProject(SolutionBase 
 solution, SolutionTas
 k solutionTask, TempFileCollection tfc, GacCache gacCache, 
 ReferencesResolver re
 ferencesResolver, DirectoryInfo outputDir, String projectPath)
at NAnt.VSNet.ProjectFactory.LoadProject(SolutionBase 
 solution, SolutionTask
 solutionTask, TempFileCollection tfc, GacCache gacCache, 
 ReferencesResolver refe
 rencesResolver, DirectoryInfo outputDir, String path)
at NAnt.VSNet.SolutionBase.LoadProjects(GacCache gacCache, 
 ReferencesResolver
  refResolver)
at NAnt.VSNet.Everett.Solution..ctor(String 
 solutionContent, SolutionTask sol
 utionTask, TempFileCollection tfc, GacCache gacCache, 
 ReferencesResolver refReso
 lver)
at NAnt.VSNet.SolutionFactory.LoadSolution(SolutionTask 
 solutionTask, TempFil
 eCollection tfc, GacCache gacCache, ReferencesResolver refResolver)
at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
at NAnt.Core.Tasks.CallTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
at NAnt.Core.Project.Execute()
   nbsp; at NAnt.Core.Project.Run()
  
 Please send bug report to 
 nant-developers@lists.sourceforge.net 
 mailto:nant-developers@lists.sourceforge.net .
  
 Total time: 2.5 seconds.
 --
 --
 Thanks.
 Regards,
 Sanjiv
 
 
 
 New Yahoo! Messenger with Voice. 
 http://us.rd.yahoo.com/mail_us/taglines/postman4/*http://us.r
 d.yahoo.com/evt=39666/*http://beta.messenger.yahoo.com  Call 
 regular phones from your PC for low, low rates.
 



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Internal error: illegal characters in exec call

2006-04-23 Thread Gert Driesen
 

 -Original Message-
 From: Gert Driesen [mailto:[EMAIL PROTECTED] 
 Sent: zondag 23 april 2006 11:14
 To: 'Trevor Misfeldt'; 'nant-developers@lists.sourceforge.net'
 Subject: RE: [nant-dev] Internal error: illegal characters in 
 exec call
 
  
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On 
  Behalf Of Trevor Misfeldt
  Sent: maandag 27 maart 2006 6:01
  To: nant-developers@lists.sourceforge.net
  Subject: [nant-dev] Internal error: illegal characters in exec call
  
  
  I got this error with this line:
  
  exec program=csc /t:library /platform:x86
  /addmodule:../Shared/NMathShared.netmodule
  /addmodule:../Kernel/NMathKernel.netmodule 
 /out:NMathCore.dll *.cs/
  
  The execution works fine from the command-line. Should I be escaping
  characters there? 
 
 You should use arg element to specify the commandline 
 argument for csc:
 
 exec program=csc
   arg value=/t:library /
   arg value=/platform:x86 /
   ...
 /exec
 
  BTW, I'm doing this 'cause I don't see a platform option on 
  csc yet. I'm
  using a nightly build from a few days ago.
 
 I'll add this asap.

I've committed the necessary changes to cvs, and I'm uploading a new nighlty
build right now.

Gert



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] The system cannot find the path specified

2006-04-21 Thread Gert Driesen
Ahmed,

Please provide a verbose build log (NAnt.exe -verbose).

Also, I suggest upgrading to a recent nightly build
(http://nant.sourceforge.net/nightly/latest).

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Ahmed, Shabana
 Sent: vrijdag 21 april 2006 18:14
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] The system cannot find the path specified
 
 Has anyone ever encountered this error saying The system 
 cannot find the path specified when you try to run any of 
 the examples that come with NANT, like say hello world. I 
 have Nant set up on my pc at c:\nant\0.84. I also set the 
 path in the environment variables to the c:\nant\0.84\bin. I 
 do the following at command prompt. 
  
 Navigate to c:\nant\0.84\bin\nant-help. This works fine. But 
 when I do this
  
 c:\nant\0.84\examples\helloworld\nant or 
 c:\nant\0.84\examples\nant. I get the following error. The 
 system cannot find the path specified.
  
 The strangest thing is this. I did the same untill noon 
 yesterday and it worked fine. I mean it performed the build. 
 But form evening yesterday, I keep getting this error. I have 
 pondered over but no clue yet. So, I though let me see if you 
 guys had a similar issue ever.
  
   I  have uninstalled Nant, reinstalled, restarted my pc, 
 reset the path variable. But, no luck yet. Please do let me 
 know if you have any suggestions. I also tried:
  
 C:\nant\0.84\examples\nant -buildfile:examples.build. It give 
 the same damn error.
  
 Please let me know if anything occurs to you.
  
 Thanks a lot,
 Shabana
 



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] The system cannot find the path specified

2006-04-21 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Ahmed, Shabana
 Sent: vrijdag 21 april 2006 18:31
 To: Gert Driesen; nant-developers@lists.sourceforge.net
 Subject: RE: [nant-dev] The system cannot find the path specified
 
 I am not sure if this is how I get tot he verbose. But, I got 
 the latest nightly build and this is the error I get. I am 
 still unable to build the examples. Please let me know what u 
 think. Thanks.

Run NAnt.exe -verbose in the examples directory and send me that output.

Gert



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Custom tasks from XML / using dynamic assemblies

2006-03-16 Thread Gert Driesen
Hi Christian,

I've fixed the dynamic assembly issue locally, and commit it to cvs in a few
minutes.

I'll let you know when I've finished uploading a new nightly build for you
to test.

Gert 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Christian Birkl
 Sent: donderdag 16 maart 2006 20:03
 To: Michael O'Brien
 Cc: nant-developers@lists.sourceforge.net
 Subject: Re: [nant-dev] Custom tasks from XML / using dynamic 
 assemblies
 
 Oh i think i forgot to mention you'll propably need the 
 latest nightly-build since there's a new public TaskBuilder() 
 constructor overload which isn't (?).
  
 Also forgot three other changes, remove the variable 
 dynAssemblyFileName and change your calls of 
 DefineDynamicModule and DefineDynamicAssembly w/o the use of 
 a filename. The last one is to change the 
 AssemblyBuilderAccess enum from RunAndSave to just Run. 
 
  
 2006/3/16, Michael O'Brien [EMAIL PROTECTED]: 
 
   Hi Christian,
   
   hooking ProcessExit doesn't seem to work, I think 
 because this occurs
   before the AppDomains are unloaded? Not sure about this 
 but Chris 
   Brumme has a post at
   
 http://blogs.msdn.com/cbrumme/archive/2003/08/20/51504.aspx which
   seems to imply this, if I've read it correctly. In any 
 case, the event 
   is fired, but the file isn't deleted because there is 
 an open lock on
   it.
   
   There is another old trick used when you want to load 
 an assembly
   without locking its file, which is to load its contents 
 into a byte 
   array, then call Assembly.Load(byte[]). The loaded 
 assembly then takes
   its location from the currently executing assembly (or 
 possibly the
   primary assembly). Unfortunately NAnt.Core.TaskBuilder 
 is tied quite
   closely to the assembly's file name, and this doesn't 
 work. Maybe
   refactoring this class to include a TaskBuilder(Type t) 
 constructor
   could help here? I'm more than happy to give this a try 
 if it sounds
   like a good idea. 
   
   If you want to have a try yourself, the code is at
   http://mcobrien.org/files/NantXmlTasks.zip. The code is 
 a bit rough at
   the moment, but CustomTaskBuilderTask does the 
 Reflection.Emit work,
   and BaseCustomTask simplifies everything by containing 
 most of the
   code the custom tasks use.
   
   cheers
   Michael
   
   On 14/03/06, Christian Birkl  
 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  wrote:
   
   
   
Hi Michael,
   
Why not just hook to ProcessExit Event of the current 
 AppDomain?
   
AppDomain.CurrentDomain.ProcessExit += new 
EventHandler(CurrentDomain_ProcessExit);
   
private void CurrentDomain_ProcessExit(object sender,
EventArgs e) {
 foreach (string myDynAssFile in DynAssFiles)
  System.IO.File.Delete (myDynAssFile);
}
   
Or depending on your type of generation method don't 
 use any file based
dynamic assemblies, as far as i remember it is 
 possible to generate In
Memory Assemblies (TypeBuilder, MethodBuilder, ...) 
 w/o the need to store 
your assembly to disk.
   
Anyway, cool idea :-) Indeed a nice to have feature 
 which would nicely fit
into NAntContrib or better NAnt ;-)
   
Christian
   
2006/3/14, Michael O'Brien  [EMAIL PROTECTED]:
   
 Hi everyone,

 I'm new on this list, so I hope this it's the right 
 place to discuss
 this, but I've written a custom task that allows 
 buildfile authors to 
 define new tasks using XML (see below for details). 
 It works well, but
 I have one problem: I generate a dynamic assembly 
 when it executes
 which it seems has to be persisted to disk (mainly because 
 TypeFactory.ScanTypeForTasks calls the Location 
 property on my dynamic
 assembly). As such, the assembly is left over on 
 disk when the script
 finishes executing, which is pretty ugly. 

 Does anyone know if there is any way to avoid this, 
 either by managing
 to add a task from my dynamic assembly, or ensuring 
 the assembly is
 deleted when the script finishes? 

 For the interested, my task works as in the 
 following example -- the
 customTask element defines a new task that 
 accepts a list of
 parameters, which are passed to the rest of the 
 customTask block 
 when the logMessage element appears. We're using 
 it quite a bit in
 some complex scripts we have to refactor otherwise 
 complex targets. If
 you'd like the C# source to this, just ask and I'll 
 put it on a 
 server.

 thanks
 Michael

 -- example follows:
 customTask name=logMessage
   parameters
   

Re: [nant-dev] New service task action types

2006-03-15 Thread Gert Driesen

 - Original Message - 
 From: Crawford, Christina [EMAIL PROTECTED]
 To: nant-developers@lists.sourceforge.net
 Sent: Wednesday, March 15, 2006 8:24 PM
 Subject: [nant-dev] New service task action types


 Request new action types to the Nant servicecontroller task:

 Uninstall a service
 Install a service

Not sure if those should be part of the servicecontroller task.

 Check to see if a service in installed or not

We could add a function for this. Would you want to try to submit a patch
for this ?

Gert




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Custom tasks from XML / using dynamic assemblies

2006-03-14 Thread Gert Driesen
Hi Michael,

Do you have a small repro you can share ?

Gert 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Michael O'Brien
 Sent: dinsdag 14 maart 2006 16:19
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Custom tasks from XML / using dynamic assemblies
 
 Hi everyone,
 
 I'm new on this list, so I hope this it's the right place to discuss
 this, but I've written a custom task that allows buildfile authors to
 define new tasks using XML (see below for details). It works well, but
 I have one problem: I generate a dynamic assembly when it executes
 which it seems has to be persisted to disk (mainly because
 TypeFactory.ScanTypeForTasks calls the Location property on my dynamic
 assembly). As such, the assembly is left over on disk when the script
 finishes executing, which is pretty ugly.
 
 Does anyone know if there is any way to avoid this, either by managing
 to add a task from my dynamic assembly, or ensuring the assembly is
 deleted when the script finishes?
 
 For the interested, my task works as in the following example -- the
 customTask element defines a new task that accepts a list of
 parameters, which are passed to the rest of the customTask block
 when the logMessage element appears. We're using it quite a bit in
 some complex scripts we have to refactor otherwise complex targets. If
 you'd like the C# source to this, just ask and I'll put it on a
 server.
 
 thanks
 Michael
 
 -- example follows:
 customTask name=logMessage
parameters
   parameter parameterName=msg required=true /
/parameters
   
echo message=${msg}/
 /customTask
   
 logMessage msg=hi there / !-- prints hi there to the console --
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language
 that extends applications into web and mobile media. Attend 
 the live webcast
 and join the prime developer group breaking into this new 
 coding territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers
 



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] resgen speed

2006-02-07 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: dinsdag 7 februari 2006 8:03
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] resgen speed
 
 Gert,
  
 you wrote (in response to one issue report):
 
  Resgen should be a lot faster in the nightly builds of 
  NAnt (http://nant.sourceforge.net/nightly/latest).
 
  Can you try this and let us know if performance is acceptable ?
  
 I tried and there is very significant speed improvement 
 (45min-17min). I believe it's on resource handling. Where 
 was the catch?

We now first check whether a resx might contain references to non-system
types, and if not, do not bother copying the referenced assemblies to a temp
directory to allow resgen to resolve these types.

Note: on .NET 2.0, we do not need to copy the referenced assemblies at all
(or check whether copying is needed), as resgen now has command line options
for passing a set of referenced assemblies.

Gert



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] resgen speed

2006-02-07 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: dinsdag 7 februari 2006 10:33
 To: 'Gert Driesen'; nant-developers@lists.sourceforge.net
 Subject: RE: [nant-dev] resgen speed
 
 Good, thanks for explanation.
 
 btw: (that one I forgot to write before :)
 
 If (targetframework==framework_nant_is_running on) {
   we could use ResouceWriter class as someone suggested?
   is it only condition or there are other catches?
 }

That would be an option, yes. We'd need to perform this in a separate
appdomain, to avoid having the default appdomain cluttered with assemblies
from every project that is being built.

But I'm not sure we want to maintant two separate implementations.

 Since I think, this condition is usually met, it could be 
 worth of. Mainly
 since in large solutions, resgen time is crutial (every ms counts).

I understand your pain ...

Gert



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Please give me the solution for the problem ASAP-Thanks

2006-02-01 Thread Gert Driesen
Arun,

Are you sure you've installed NAnt correctly ?

Gert 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of arun kumar
 Sent: zaterdag 14 januari 2006 10:58
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Please give me the solution for the 
 problem ASAP-Thanks
 
 Hi,
 When i execute the Nant build file,its showing the following error
  
 Buildfile: file:///C:/Documents and Settings/Arun/My 
 Documents/Visual Studio Projects/NAntBuildAndNunit/Nantbuild.build 
 Target framework: Microsoft .NET Framework 1.1 
 Target(s) specified: test 
 [property] Read-only property build.dir cannot be overwritten. 
 build: 
 test: 
 BUILD FAILED- 0 non-fatal error(s), 1 warning(s) 
 INTERNAL ERROR 
 System.IO.FileLoadException: The located assembly 'nunit. 
 core' is not strongly named. 
 File name: nunit.core 
 at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask() 
 at NAnt.Core.Task.Execute() 
 at NAnt.Core.Target.Execute() 
 at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies) 
 at NAnt.Core.Project.Execute() 
 at NAnt.Core.Project.Run() 
 Please send bug report to [EMAIL PROTECTED] 
 Total time: 1.5 seconds. 
 
 
 
 Yahoo! Photos
 Got holiday prints? See all the ways 
 http://us.rd.yahoo.com/mail_us/taglines/holidayprints/*http:/
/pa.yahoo.com/
*http://us.rd.yahoo.com/mail_us/taglines/photos/evt=38089/*htt
p://pg.photos.yahoo.com/ph//print_splash  to get quality prints  in your
hands ASAP.
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Build against .NET FX 2.0 Release C# Projects

2006-02-01 Thread Gert Driesen
Rick,

The solution task currently does not support .NET 2.0 solutions or
projects.

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Rick Garibay
 Sent: dinsdag 24 januari 2006 22:31
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Build against .NET FX 2.0 Release C# Projects
 
  Error.txt I am trying to build a .NET 2.0 project. I know that VS
 2005 solutions aren't supported yet, but are projects supported?
 
 This is what I am running at the command line: nant -t:net-2.0 build
 where build is the name of my target.
 
 Also, I changed all references in the framework element where the name
 attribute is net-2.0 from the BETA 1 build to the release version of
 v2.0.50727 as follows:
 
 framework 
 name=net-2.0 
 family=net 
 version=2.0 
 description=Microsoft .NET Framework 2.0 
 runtimeengine=
 sdkdirectory=${path::combine(sdkInstallRoot,
 'bin')} 
 frameworkdirectory=${path::combine(installRoot,
 'v2.0.50727')} 
  
 frameworkassemblydirectory=${path::combine(installRoot, 
 'v2.0.50727')}
 clrversion=2.0.50727
 
 
 
 Any help greatly appreciated.
 
 Rick G. Garibay
 Corporate Systems
 Development Lead, MCP
 DriveTime Sales  Finance Co.
 
 
 
 
 
 
 This email message and any attachments contain information 
 which may be privileged and confidential. If you are not the 
 intended recipient or have received this transmission in 
 error, please notify the sender immediately and destroy all 
 electronic and hard copies of the communication, including 
 attachments. Any disclosure, copying, distribution or use of 
 this information is strictly prohibited.  Thank you.
 
 
 
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Nant Internal Error

2006-02-01 Thread Gert Driesen
Mohammed,

I ran into this issue myself once, but I could not reproduce it later on.

Can you consistently reproduce this issue ?

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Farooq Mohammed
 Sent: donderdag 5 januari 2006 18:39
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Nant Internal Error
 
 INTERNAL ERROR
 
  
 
 System.ArgumentException: Invalid File or Directory attributes value.
 
at System.IO.File.SetAttributes(String path, 
 FileAttributes fileAttributes)
 
at NAnt.Core.Tasks.CopyTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.TaskContainer.ExecuteChildTasks()
 
at NAnt.Core.Tasks.LoopTask.ExecuteChildTasks()
 
at NAnt.Core.Tasks.LoopTask.DoWork(String[] propVals)
 
at NAnt.Core.Tasks.LoopTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.TaskContainer.ExecuteChildTasks()
 
at NAnt.Core.Tasks.IfTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.TaskContainer.ExecuteChildTasks()
 
at NAnt.Core.Tasks.IfTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.Target.Execute()
 
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
 
at NAnt.Core.Tasks.CallTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.TaskContainer.ExecuteChildTasks()
 
at NAnt.Core.Tasks.IfTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.TaskContainer.ExecuteChildTasks()
 
at NAnt.Core.Tasks.IfTask.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.Target.Execute()
 
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
 
at NAnt.Core.Project.Execute()
 
at NAnt.Core.Project.Run()
 
  
 
 Please send bug report to [EMAIL PROTECTED]
 
  
 
 Total time: 1.5 seconds.
 
  
 
 CONFIDENTIAL NOTICE: This message is intended only for the use of the 
 
 individual or entity to which it is addressed and may contain 
 information 
 
 that is privileged, confidential and exempt from disclosure 
 under applicable 
 
 law. If the reader of this message is not the intended 
 recipient, or the 
 
 employee or agent responsible for delivering the message to 
 the intended 
 
 recipient, you are hereby notified that any dissemination, 
 distribution or 
 
 copying of this communication is prohibited. Please notify us 
 immediately 
 
 by telephone if this message was transmitted in error. Thank you. 
 
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] nant not working for web application

2006-02-01 Thread Gert Driesen
Jayakumar,

Usage of WebDAV for deployment is actually deprecated, but you could try
using a more recent version of NAnt
(http://nant.sourceforge.net/nightly/latest).

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Gnanadesikan Jayakumar
 Sent: dinsdag 3 januari 2006 8:31
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] nant not working for web application
 
 Hi, 
 
 I have compiled the web project using nant.exe. it is giving 
 forbidden error. when i gave script source access option 
 checked in IIS, it is throwing the error shown below:
 
 Please kindly look thru it and give me the solution as soon 
 as possible 
 
 regards, 
 Jayakumar G. 
 
 Error thrown: 
 
 Buildfile: file:///C:/Projects/datauseradmin/datauseradmin.build 
 Target(s) specified: build 
 
 build: 
 
 clean: 
 
[delete] Deleting 0 files. 
  [solution] Starting solution build. 
 
 BUILD FAILED 
 
 INTERNAL ERROR 
 
 System.ArgumentException: URI formats are not supported. 
at System.IO.Path.GetFullPathInternal(String path) 
at System.IO.FileInfo..ctor(String fileName) 
at NAnt.VSNet.Project.Load(Solution sln, String 
 projectPath) in C:\DOCUME~1\A 
 DMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.VSNet\Project.cs:line 150 
at NAnt.VSNet.ProjectFactory.LoadProject(Solution sln, 
 SolutionTask slnTask, 
 TempFileCollection tfc, GacCache gacCache, DirectoryInfo 
 outputDir, String path) 
  in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.VSNet\Pr
 ojectFactory.c 
 s:line 72 
at NAnt.VSNet.Solution.LoadProjects(GacCache gacCache) in 
 C:\DOCUME~1\ADMINI~ 
 1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.VSNet\Solution.cs:line 535 
at NAnt.VSNet.Solution..ctor(FileInfo solutionFile, 
 ArrayList additionalProje 
 cts, ArrayList referenceProjects, TempFileCollection tfc, 
 SolutionTask solutionT 
 ask, WebMapCollection webMaps, FileSet excludesProjects, 
 DirectoryInfo outputDir 
 , GacCache gacCache) in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.VS 
 Net\Solution.cs:line 130 
at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in 
 C:\DOCUME~1\ADMINI~1\LOCALS 
 ~1\Temp\tmp26.tmp\src\NAnt.VSNet\Tasks\SolutionTask.cs:line 365 
at NAnt.Core.Task.Execute() in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\s 
 rc\NAnt.Core\Task.cs:line 151 
at NAnt.Core.Target.Execute() in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp 
 \src\NAnt.Core\Target.cs:line 249 
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies) in 
  
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Pro
 ject.cs:line 892 
at NAnt.Core.Project.Execute() in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tm 
 p\src\NAnt.Core\Project.cs:line 849 
at NAnt.Core.Project.Run() in 
 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\sr 
 c\NAnt.Core\Project.cs:line 917 
 
  
 The information contained in this e-mail may be confidential 
 and is intended solely for the use of the named addressee.
 Access, copying or re-use of the e-mail or any information 
 contained therein by any other person is not authorized.
 If you are not the intended recipient please notify us 
 immediately by returning the e-mail to the originator.(16b)
  
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] NAnt install error

2006-02-01 Thread Gert Driesen
Jeremy,

You ran into a known issue for NAnt 0.85 RC3, which was fixed since. 

Try using a recent nightly build
(http://nant.sourceforge.net/nightly/latest).

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Jeremy Veeder
 Sent: maandag 30 januari 2006 11:57
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] NAnt install error
 
 What could be the problem with the installation? 
 Thanks 
 Jeremy 
 
 
 Here is the log:- 
 
 Setting environment for using Microsoft Visual Studio .NET 
 2003 tools. 
 (If you have another version of Visual Studio or Visual C++ 
 installed and wish 
 to use its tools from the command line, run vcvars32.bat for 
 that version.) 
 
 H:\c: 
 
 C:\cd C:\Documents and Settings\jeremyve\Desktop\nant-0.85-rc3 
 
 C:\Documents and 
 Settings\jeremyve\Desktop\nant-0.85-rc3nmake -f 
 Makefile.nmake install prefix=C:\Program Files 
 
 Microsoft (R) Program Maintenance Utility Version 7.10.3077 
 Copyright (C) Microsoft Corporation.  All rights reserved. 
 
 if not exist bootstrap md bootstrap 
 if not exist bootstrap\lib md bootstrap\lib 
 xcopy lib bootstrap\lib /S /Y /Q 
 36 File(s) copied 
 copy lib\log4net.dll bootstrap 
 1 file(s) copied. 
 copy src\NAnt.Console\App.config bootstrap\NAnt.exe.config 
 1 file(s) copied. 
  bootstrap\NAnt.exe -f:NAnt.build install 
 -D:install.prefix=C:\ProgramFiles 
 NAnt 0.85 (Build 0.85.1932.0; rc3; 16/04/2005) 
 Copyright (C) 2001-2005 Gerry Shaw 
 http://nant.sourceforge.net http://nant.sourceforge.net  
 
 Buildfile: file:///C:/Documents file:///C:/Documents  and 
 Settings/jeremyve/Desktop/nant-0.85-rc3/NAnt.build 
 Target framework: Microsoft .NET Framework 1.1 
 Target(s) specified: install 
 
[tstamp] Monday 30 January 2006 12:38:55. 
 
 init: 
 
 
 debug: 
 
 
 set-framework-configuration: 
 
 
 set-net-1.1-framework-configuration: 
 
 
 build: 
 
  [echo] Build Directory is C:\Documents and 
 Settings\jeremyve\Desktop\nant-0.85-rc3/build/net-1.1.win32/na
 nt-0.85-debug
 
  [nant] C:\Documents and 
 Settings\jeremyve\Desktop\nant-0.85-rc3\src\NAnt.Core\NAnt.Cor
 e.build build 
 Buildfile: file:///C:/Documents 
 file:///C:/Documents  and 
 Settings/jeremyve/Desktop/nant-0.85-rc3/src/NAnt.Core/NAnt.Core.build 
 Target framework: Microsoft .NET Framework 1.1 
 Target(s) specified: build 
 
 
 build: 
 
 
 BUILD FAILED 
 
 INTERNAL ERROR 
 
 
 System.Resources.MissingManifestResourceException: Could not 
 find any resources appropriate for the specified culture (or 
 the neutral culture) in the given assembly.  Make sure 
 Strings.resources was correctly embedded or linked into 
 assembly NAnt.DotNetTasks.
 
 baseName: Strings  locationInfo: null  resource 
 file name: Strings.resources  assembly: NAnt.DotNetTasks, 
 Version=0.85.1932.0, Culture=neutral, PublicKeyToken=null
 
at 
 System.Resources.ResourceManager.InternalGetResourceSet(Cultur
 eInfo culture, Boolean createIfNotExists, Boolean tryParents)
 
at 
 System.Resources.ResourceManager.InternalGetResourceSet(Cultur
 eInfo culture, Boolean createIfNotExists, Boolean tryParents)
 
at 
 System.Resources.ResourceManager.InternalGetResourceSet(Cultur
 eInfo culture, Boolean createIfNotExists, Boolean tryParents)
 
at 
 System.Resources.ResourceManager.GetString(String name, 
 CultureInfo culture) 
at 
 NAnt.Core.Util.ResourceUtils.GetString(String name, 
 CultureInfo culture, Assembly assembly) 
at NAnt.Core.Util.ResourceUtils.GetString(String name) 
at NAnt.DotNet.Tasks.CscTask.NeedsCompiling() 
at NAnt.DotNet.Tasks.CompilerBase.ExecuteTask() 
at NAnt.Core.Task.Execute() 
at NAnt.Core.Target.Execute() 
at NAnt.Core.Project.Execute(String 
 targetName, Boolean forceDependencies) 
at NAnt.Core.Project.Execute() 
at NAnt.Core.Project.Run() 
 
 Please send bug report to 
 [EMAIL PROTECTED] 
 
 Total time: 0.2 seconds. 
 
 
 BUILD FAILED 
 
 Nested build failed.  Refer to build log for exact reason. 
 
 Total time: 0.8 seconds. 
 
 NMAKE : fatal error U1077: 'bootstrap\NAnt.exe' : return code '0x1' 
 Stop. 
 
 --
 -
 This e-mail message may contain confidential, commercial and 
 privileged information or data that constitute proprietary 
 information of Cellcom Israel Ltd. Any review or distribution 
 by others is strictly prohibited. If you are not the intended 
 recipient you are hereby notified that any use of this 
 information or data by any other person is absolutely 
 prohibited. If you are not the intended recipient, 

Re: [nant-dev] New XML tasks and functions

2006-01-30 Thread Gert Driesen
Martin,

Overloading of functions is not (yet) supported. I'm definitely in favor of
this, but if I recall correctly Ian and Jarek ruled against this in favor of
implicit conversion of function arguments. Ian, please correct me if I'm
wrong.

Gert
- Original Message - 
From: Martin Aliger [EMAIL PROTECTED]
To: 'John Ludlow' [EMAIL PROTECTED];
nant-developers@lists.sourceforge.net
Sent: Monday, January 30, 2006 10:02 AM
Subject: RE: [nant-dev] New XML tasks and functions


Hello,

I like it very much. Expecially functions. Bad luck I personally need
namespace support, since mine xmls have some namespace in it. And even
default namespace needs specification in xpaths :-(

Maybe there could be some elegant way how to pass namespace mapping into
functions. New type come to my mind. It could be elegant perhaps.

btw: does nant functions support overloading and/or default parameter value?
bool xml::value-exists (string xmlFile, string xPath,
NamespaceMap nsMap = null)


===

Here is typical use of namespace map (taken from my real script):

   xmlpeek
file=${prjconfig}
xpath=x:Project/x:ExeName
property=newexe
failonerror=true
failonnonode=false

namespaces

namespace
prefix=x uri=http://www.gordic.cz/shared/project-config/v_1.0.0.0/
/namespaces

/xmlpeek


And sample xml file is here (changed to protect innocent):

?xml version=1.0 encoding=utf-8?
Project xmlns=http://www.gordic.cz/shared/project-config/v_1.0.0.0;
  Namefoo/Name
  Descriptionfoobar/Description
  ExeNamefootest/ExeName
/Project

===

I missed xml-foreach once too, but nowadays I do not need it. Still it could
be worth addition to NAnt(Contrib) tasks!

Martin Aliger


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On
 Behalf Of John Ludlow
 Sent: Tuesday, January 24, 2006 7:19 PM
 To: nant-developers@lists.sourceforge.net;
 nantcontrib-developer@lists.sourceforge.net
 Subject: [nant-dev] New XML tasks and functions

 Hi, there

 Recently I mentioned on the NAnt Dev list that I have been
 working on XML-handling functionality.  I've got further than
 I had last time, so I thought about summarising what I've
 done here (I'm also happy to share the code and/or binaries,
 so if you want either of these to check it out for yourself,
 just email me at [EMAIL PROTECTED]).  I've put my code
 into an assembly, tested it, and am currently contemplating
 writing some unit tests for it.
 Before I go through that, though, I wanted to get some
 feedback and a better idea of what people thought of this.

 This is what I have so far:

 Functions
 ===

 bool xml::value-exists (string xmlFile, string xPath)
 --
 ---
 Tests whether a specified xpath query returns a value.  If
 this gets a NullReferenceException (usually means an XML
 value doesn't exist).

 string xml::get-value (string xmlFile, string xPath)
 --
 -
 Gets a value returned by an XPath query.  Throws an error if
 the node specified in the xpath is not found.  Duplicates
 some of xmlpeek's functionality, but enables you to use
 ${x} syntax to get an xml value.
  This fits in with the idea that being able to use this
 functionality is nicer if all you want is information.
 However, it does not support namespaces like xmlpeek does.

 string xml::get-value-without-failing (string xmlFile, string xPath)
 --
 -
 Gets a value returned by an XPath query.  As above, but does
 not an error if the node specified in the XPath is not found,
 instead returning a blank string.

 string xml::get-xml (string xmlFile, string xPath) Gets the
 InnerXml property of an XML node returned by an XPath query.

 int xml::count (string xmlFile, string xPath) Gets the number
 of nodes in a document that match the specified XPath query.

 Tasks

 xml-foreach
 =
 Iterates through an XML document.  I thought about making
 this part of the ForEach task, but there seemed to be a
 significant difference in functionality, especially
 concerning getting  the details of each item in the
 iteration.  For this reason, I decided to make a separate task.
  The syntax is explained below:

 Attributes:
 
  - file:  string.  XML file to iterate
  - xpath:  string.  XPath.  The task will essentially iterate
 through the list of nodes that match this query.
  - index:  string.  Optional.  A property that can contain
 the index of a returned result in the node list.  You can use
 this to find this node in the doument again, especially
 useful for nested loops.  By default doesn't set any property.

 Nested elements:
 =
  - do:  The tasks to run on each iteration

  - xmlpropertybinding:  Runs XPath queries on the result,
 putting the returned value in a property.

  - xmlpropertybinding/get

 Attributes
 

RE: [nant-dev] VS 2005 project support (via MSBuild)

2005-12-30 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: vrijdag 30 december 2005 15:25
 To: ! nant
 Subject: [nant-dev] VS 2005 project support (via MSBuild)
 
 I was thinking about Reflection too. Have to try it.
 
 But - maybe, simlest solution: keep separate assembly 
 (NAnt.MSBuild) and use
 some reflection stuff from solution task to this assembly. 
 To keep current
 solution working even on 1.1/1.0 profile.

That's an option ofcourse.

 For now, I just focus to get it working. It'll certainly need 
 some time to
 tune it.

That's why we talked about including it in NAntContrib first, so no problem
here.

 btw: Do you review mine changes to NAnt.VSNet? Are they ok? 
 I'd like to keep

Nope, haven't had time yet. I'll get to it once I've sobered up ;-) lol

 msbuild stuff separate from core for while. Maybe in NAntContrib or
 elsewhere (becouse of 2.0 dependency). And those patches was needed to
 enable it.

No prob.

Thanks for the work you've put into this !

Gert



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] need VS 2005 solution task support

2005-12-09 Thread Gert Driesen

-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Friday, December 9, 2005 09:06 AM
To: 'Martin Aliger'
Cc: ''Gert Driesen'', ''Gert Driesen'', ''! nant''
Subject: Re: [nant-dev] need VS 2005 solution task support

Martin Aliger wrote:

I don't think we need to make solution task compatibility a
goal here.



I was thinking same, but first I wanted to use msbuild, I found myself in
situation where solution is used today. Even that msbuild is quite general
system, we, nant users, will call it mainly to compile vs2005 solutions. So
I rethink it, and it makes some sense to me.



Creating a solution on the fly is not something we should
support, as you need to make a bunch of assumptions anyway
(dependencies, platform, ...).



In fact, this was first issue I come around, when writing msbuild wrapper
task. Thats why I rethinked implementation. If you find more appropriate, we
could make msbuild task as direct wrapper and make another task,say
vs2005 or msbuild-solution, which could do those additional wrapping.


This sounds like a good compromise. msbuild gives you full control of 
the msbuild commandline while msbuild-solution provides a nice upgrade
path for vs2003 solution task users.

Yes, I agree that this is the right thing to do.


Good think about this on-the-fly solution creation is, that msbuild imply
dependences and project compile order from it. Exacly what our solution do
when we fed it with project fileset. Sure - there are assumption, but I
beleive they could be made configurable where appropriate.



so it sounds like there is definately a place for solution like
functionality in an msbuild wrapping task.




About namespace/packaging: would it be ok to add it to
NAntContrib first, and move it to NAnt once it has stabilized
?  This is our policy for all new tasks.



np. I do not use NAntContrib currently, but no problems with relocating to
another project. It is quite stand-alone task (depending on just
ExternalProgramBase).


Putting it NAntContrib first is the correct policy decision but I
suspect we'll have some demand to move it into main fairly soon - vs2005
support for solution has been one of the most requested features.

I think the pure msbuild wrapper task should more easily (rapidly) find its 
way to NAnt, as its built upon a stable command line interface.

If you look at the features requested by users of the current solution task, 
the msbuild-based solution task might actually be better off in NAntContrib 
as it allows more custom tailoring (and you'll find less resistance to breaking 
changes) while tasks in NAnt should be more stable and only contain generally 
useful features.

Note: I'm not saying the msbuild-based solution task is not generally useful.

Thanks for starting this Martin - I'm sure there will be many happy
solution task users.

Definitely agree with this !

Gert





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Question about nunit-gui

2005-12-09 Thread Gert Driesen

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, December 9, 2005 06:39 PM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Question about nunit-gui



 Hi,

 I'm unittesting an application that uses Firebird. In every test I shutdown
 all the connections, overwrite the data files (*.fdb), and start again.
 Well, running in console mode (nunit-console) it never fails but running
 from nunit-gui I get errors telling that the files are locked by another
 process. I'm using something like FbConnection.ClearAllPools(); to close
 everything... Why does it remain open?? Why is it different from GUI to
 console?

Please post this message to one of the NUnit mailing lists.

Thanks !

Gert




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] NAnt Error

2005-12-07 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of chellu pradeep
 Sent: dinsdag 6 december 2005 23:24
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] NAnt Error
 
 INTERNAL ERROR
  
 System.MissingMethodException: Method not found: Void 
 NAnt.Core.PropertyDictionary.Remove(System.String).
at NAnt.Contrib.Tasks.CatchElement.Catch(BuildException be)
at NAnt.Contrib.Tasks.TryCatchTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()
 Please send bug report to [EMAIL PROTECTED]
 
  
  
 How to resolve the error?? I downloaded the latest release of 
 NAnt and NAntContrib and i copied the contents of NAntContrib 
 bin folder to NAnt's bin folder so that i can use trycatch 
 task in the NAnt build fil es. After doing this i receive the 
 above errror.

You really must be mixing versions. Are you sure you're using a recent
nightly build of NAnt and Nantcontrib ?

Gert



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] need VS 2005 solution task support

2005-12-07 Thread Gert Driesen
Hi Martin,

I don't think we need to make solution task compatibility a goal here.
Creating a solution on the fly is not something we should support, as you
need to make a bunch of assumptions anyway (dependencies, platform, ...).

We should start it off as a simple wrapper for MSBuild.exe. I think it
should be closer to the nant task than the solution task.

I think we should add support for :

- properties (nested element with collection, similar to nant task)
- target(s) (string attribute or nested element with collection of targets
?)
- logger (string attribute, or nested element with class and assembly
attribute, and parameters collection ?)
- verbosity (enum attribute, do we let this coexist with our verbose
attribute ?)

Optional:

-noconsolelogger (bool attribute)
-consoleloggerparameters (nested element, containing collection of
parameters)
-noautoresponse (bool attribute)
-validate (nested element, as it should have an on/off switch and a way to
specify a schema file)

Martin: don't mean to sound negative about the work you've done. Thanks for
starting with this !!

About namespace/packaging: would it be ok to add it to NAntContrib first,
and move it to NAnt once it has stabilized ?  This is our policy for all new
tasks.

Gert


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Martin Aliger
 Sent: dinsdag 6 december 2005 21:15
 To: 'Ian MacLean'; 'Gert Driesen'
 Cc: '! nant'
 Subject: RE: [nant-dev] need VS 2005 solution task support
 
 Hello,
 
 here is first attempt to implement msbuild task for MSBuild 
 interation. To
 be a little usable for us, NAnt users, I made it atleast 
 little compatible
 with solution task. So its not a simple wrapper around 
 msbuild.exe. Mainly
 it accept fileset of projects, which msbuild itself do not. 
 Property names
 are compatible with solution task as well.
 
 I also implement function to distinguish between 
 vs2003/vs2005 projects, but
 I'm not sure if it'd be useful.
 
 For now, I place it to NAnt.DotNet project. Maybe other 
 location is more
 appropriate?
 
 No testcases yet, but they should be next step. Let me know, 
 if you like
 this approach. More attibutes/element will be needed as well, 
 I think. Ideas
 are welcomed :-)
 
 Almost forgot:
 you need to add
 task name=msbuild
 attribute 
 name=exenameMSBuild/attribute
 /task
 to NAnt.exe.config under framework name=net-2.0.
 
 Regards,
 Martin Aliger
 
 PS: I'll refactor to follow nant's conding standarts lately. Sorry for
 inconvenience. This is just a preview...
 
 Note: MSBuild from net 2.0 Beta 2 will not compile solutions 
 from VS2005
 final. Took me hour to figure :)
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] need VS 2005 solution task support

2005-12-05 Thread Gert Driesen
Ian, Martin,

Do you think we should support VS.NET 2005 solutions/projects in the solution 
task ?

As far as I can tell, we have two options for supporting this:

1. Do the full parsing, and processing of the solutions/projects ourselves, 
like we do for VS.NET 2002/2003, and use our built-in tasks (and extend these 
where required) to do the heavy work.

2. Invoke MSBuild (behind the scenes) to build VS.NET 2005 solutions/projects.

The advantage of (1) could be that it allows users to target multiple framework 
versions, but the code that is generated (behind the scenes) by VS.NET 2005 
makes it impossible to compile for older versions of .NET. However, we might be 
able to compile most code using Mono once the Mono tools support some of the 
stuff that's introduced in .NET 2.0 (eg. creating strongly typed code for 
accessing resources)

Users (build authors) can also extend the VS.NET 2005 project files. This is 
definitely not something we can support.  So, we'd be putting in a lot of 
effort just to support very basic VS.NET 2005 projects.

Option (2) makes perhaps even less sense: if we do not process the VS.NET 2005 
solutions/projects ourselves, then we cannot support more advanced options of 
the solution task for them (such as assemblyfolders, outputdir, ...). And 
if we cannot do this, then what's the benefit over using a msbuild task 
anyway ?

What do you think ?

Gert

-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, December 5, 2005 06:38 AM
To: 'Martin Aliger'
Cc: [EMAIL PROTECTED], '! nant'
Subject: Re: [nant-dev] need VS 2005 solution task support

Martin Aliger wrote:


Or, alternativelly, it should not be hard at all to write msbuild task
just as a wrapper around msbuild.exe as ccnet do it. Something like ant
already do. Not bad idea. What others think about this? Maybe I'd not give
up mine hard-earned build scripts after all :-)



I think thats a great idea. I think that would be a big help for the
many people migrating to vs2005 but wanting to retain their existing
NAnt build scripts.

Ian






---




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers






---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] System.NullReferenceException after upgrading project to .NET 2.0

2005-12-05 Thread Gert Driesen
Ben,

The solution task does not support VS.NET 2005 solutions/projects.

Note: we do support using VS.NET 2002/2003 solutions/projects and building the 
assemblies targeting .NET 2.0

Also, I'd advise you to upgrade to a more recent version of NAnt 
(http://nant.sourceforge.net/nightly/latest).

Gert

-Original Message-
From: Ben Hill [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 4, 2005 01:22 AM
To: nant-developers@lists.sourceforge.net
Cc: 'Sacha Clayton'
Subject: [nant-dev] System.NullReferenceException after upgrading project to 
.NET 2.0

I recently upgraded our project to .NET 2.0.  After adding a ProjectGuid
to our csproj file (as instructed by a previous nant build error), I
receive the following error:  (I have included the contents of our build
file below, as well)

I have downloaded the latest nightly build of NANT.

System.NullReferenceException: Object reference not set to an instance
of an object.
   at NAnt.VSNet.ProjectFactory.IsUrl(String fileName) in
e:\cvs\nant\src\NAnt.VSNet\ProjectFactory.cs:line 103
   at NAnt.VSNet.ManagedProjectBase.get_ProjectPath() in
e:\cvs\nant\src\NAnt.VSNet\ManagedProjectBase.cs:line 222
   at NAnt.VSNet.CSharpProject.VerifyProjectXml(XmlElement docElement)
in e:\cvs\nant\src\NAnt.VSNet\CSharpProject.cs:line 65
   at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition,
SolutionTask solutionTask, TempFileCollection temporaryFiles, GacCac
e gacCache, ReferencesResolver referencesResolver, DirectoryInfo
outputDir) in e:\cvs\nant\src\NAnt.VSNet\ProjectBase.cs:line 72
   at NAnt.VSNet.ManagedProjectBase..ctor(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solut
onTask, TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver, DirectoryInfo outputDir) in e:\cvs\nant\src\NA
t.VSNet\ManagedProjectBase.cs:line 42
   at NAnt.VSNet.CSharpProject..ctor(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solutionTa
k, TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver, DirectoryInfo outputDir) in e:\cvs\nant\src\NAnt.VS
et\CSharpProject.cs:line 36
   at NAnt.VSNet.ProjectFactory.CreateProject(SolutionBase solution,
SolutionTask solutionTask, TempFileCollection tfc, GacCache
acCache, ReferencesResolver referencesResolver, DirectoryInfo outputDir,
String projectPath) in e:\cvs\nant\src\NAnt.VSNet\Projec
Factory.cs:line 179
   at NAnt.VSNet.ProjectFactory.LoadProject(SolutionBase solution,
SolutionTask solutionTask, TempFileCollection tfc, GacCache ga
Cache, ReferencesResolver referencesResolver, DirectoryInfo outputDir,
String path) in e:\cvs\nant\src\NAnt.VSNet\ProjectFactory.
s:line 94
   at NAnt.VSNet.SolutionBase.LoadProjects(GacCache gacCache,
ReferencesResolver refResolver, Hashtable explicitProjectDependenci
s) in e:\cvs\nant\src\NAnt.VSNet\SolutionBase.cs:line 401
   at NAnt.VSNet.SolutionBase..ctor(SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refR
solver) in e:\cvs\nant\src\NAnt.VSNet\SolutionBase.cs:line 44
   at NAnt.VSNet.GenericSolution..ctor(SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver r
fResolver) in e:\cvs\nant\src\NAnt.VSNet\GenericSolution.cs:line 36
   at NAnt.VSNet.SolutionFactory.LoadSolution(SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesRes
lver refResolver) in e:\cvs\nant\src\NAnt.VSNet\SolutionFactory.cs:line 54
   at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in
e:\cvs\nant\src\NAnt.VSNet\Tasks\SolutionTask.cs:line 406
   at NAnt.Core.Task.Execute() in e:\cvs\nant\src\NAnt.Core\Task.cs:line 171
   at NAnt.Core.Target.Execute() in
e:\cvs\nant\src\NAnt.Core\Target.cs:line 247
   at NAnt.Core.Project.Execute(String targetName, Boolean
forceDependencies) in e:\cvs\nant\src\NAnt.Core\Project.cs:line 885
   at NAnt.Core.Project.Execute() in
e:\cvs\nant\src\NAnt.Core\Project.cs:line 837
   at NAnt.Core.Project.Run() in
e:\cvs\nant\src\NAnt.Core\Project.cs:line 922

Please send bug report to [EMAIL PROTECTED]


BUILD FILE

?xml version=1.0 ?
project name=Lorien default=build basedir=.
property name=site.parentdir value=c:\webroot /
property name=site.name value=Lorien /
property name=site.rootdir value=${path::combine(site.parentdir,
site.name)} /

property name=nant.settings.currentframework value=net-2.0 /
property name=configuration value=release /
property name=bin value=./WebRoot/bin /
property name=obj value=./obj /
   
target name=build description=Compile all files
solution configuration=${configuration}
projects
include name=Lorien.csproj /
/projects
/solution
/target
target name=test description=Test with NUnit depends=build
nunit2
formatter type=Plain /
test assemblyname=${bin}/Lorien.dll /
/nunit2
/target
target name=install description=Install files depends=build
   

Re: [nant-dev] Bug Report

2005-12-05 Thread Gert Driesen
Brian,

Can you send me a small repro for this issue ?

Thanks !

Gert
-Original Message-
From: Rassier, Brian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 10:53 PM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Bug Report

My last NAnt failure asked to send a bug report to this address.  The
error happened when compiling a VB6 object with the vb6 task.  Let me
know if more details are needed.  The following is the stack trace:

INTERNAL ERROR

System.FormatException: Input string was not in a correct format.
   at System.Number.ParseDouble(String s, NumberStyles style,
NumberFormatInfo info)
   at System.Double.Parse(String s, NumberStyles style, IFormatProvider
provider)
   at NAnt.Contrib.Tasks.Vb6Task.VB6GetTypeLibFile(Guid guid, UInt16
major, UInt16 minor16, UInt32 lcid)
   at NAnt.Contrib.Tasks.Vb6Task.ParseProjectFile(String projectFile,
FileSet sources, FileSet references)
   at NAnt.Contrib.Tasks.Vb6Task.ProjectNeedsCompiling(String
projectFile)
   at NAnt.Contrib.Tasks.Vb6Task.NeedsCompiling()
   at NAnt.Contrib.Tasks.Vb6Task.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(String targetName, Boolean
forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()

--
NOTICE: The information contained in this electronic mail message is 
confidential and intended only for certain recipients.  If you are not an 
intended recipient, you are hereby notified that any disclosure, reproduction, 
distribution or other use of this communication and any attachments is 
strictly prohibited.  If you have received this communication in error, please 
notify the sender by reply transmission and delete the message without copying 
or disclosing it.
==





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] possible bug with multiple script segments?

2005-11-25 Thread Gert Driesen
Aaron,

Can you try using a recent nightly build ? I think we fixed this issue a
while ago.

Gert

- Original Message - 
From: Aaron Neerenberg [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Cc: [EMAIL PROTECTED]; Aaron Neerenberg
[EMAIL PROTECTED]
Sent: Thursday, November 17, 2005 7:08 PM
Subject: [nant-dev] possible bug with multiple script segments?


Here's an interesting one.

I have attached 3 files, default.build, default.1s.build, and
default.2s.build.

Default.build is a small NAnt project file containing 2 script segments
with VB functions.
Default.1s.build is the same file, but with one of the script segments
removed.
Default.2s.build is the same file, but with the other segment removed
instead.

When I attempt to use default.build, I receive a non-fatal, internal
error as follows:

C:\wc_buildnant -buildfile:default.build foobleh
NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005)
Copyright (C) 2001-2005 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///C:/wc_build/default.build
Target framework: Microsoft .NET Framework 1.1
Target(s) specified: foobleh

   [script] Scanning assembly e_0f3wc7 for extensions.
   [script] Scanning assembly lywj0gwb for extensions.
   [script] Failure scanning
nant46a205bf050d4330885efdc9c8d50bd9+foo4_c, lywj0gwb, Version=0.0.0.0,
Culture=neutral, PublicKeyTo
ken=null for tasks.

BUILD FAILED - 1 non-fatal error(s), 0 warning(s)

INTERNAL ERROR

System.ArgumentNullException: Value cannot be null.
Parameter name: element
   at System.Attribute.GetCustomAttributes(MemberInfo element, Type
type, Boolean inherit)
   at System.Attribute.GetCustomAttribute(MemberInfo element, Type
attributeType, Boolean inherit)
   at NAnt.Core.TaskBuilder..ctor(String className, String
assemblyFileName)
   at NAnt.Core.TypeFactory.ScanTypeForTasks(Type type, Task task)
   at NAnt.Core.TypeFactory.ScanAssembly(Assembly assembly, Task task)
   at NAnt.DotNet.Tasks.ScriptTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Project.InitializeProjectDocument(XmlDocument doc)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()

Please send bug report to [EMAIL PROTECTED]

Total time: 0.8 seconds.

On the other hand, using default.1s.build or default.2s.build,
everything works as I would expect:

C:\wc_buildnant -buildfile:default.1s.build foobleh
NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005)
Copyright (C) 2001-2005 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///C:/wc_build/default.1s.build
Target framework: Microsoft .NET Framework 1.1
Target(s) specified: foobleh

   [script] Scanning assembly hlbeavjq for extensions.

foobleh:

 [echo] 54321

BUILD SUCCEEDED

Total time: 0.4 seconds.


C:\wc_buildnant -buildfile:default.2s.build foobleh
NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005)
Copyright (C) 2001-2005 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///C:/wc_build/default.2s.build
Target framework: Microsoft .NET Framework 1.1
Target(s) specified: foobleh

   [script] Scanning assembly bnllose5 for extensions.

foobleh:

 [echo] 12345

BUILD SUCCEEDED

Total time: 0.4 seconds.

Does anyone have any ideas what might be wrong with default.build or
with NAnt?

Please note that I am not a member of this mailing list.

Thank you,
Aaron Neerenberg
Cascade Microtech


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Which mono version am I using?

2005-11-20 Thread Gert Driesen
Kevin,

We use pkg-config to determine the location of Mono on Linux.

If you want to modify the version of Mono that is detected by NAnt, you'll
have modify the PKG_CONFIG_PATH export.

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Kevin
 Sent: zondag 20 november 2005 2:20
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Which mono version am I using?
 
 I have multiple versions of mono installed on a Linux 
 configuration.  Is there a way to tell which version NAnt is 
 picking up?  I tried reading through the NAnt.exe.config, but 
 couldn't really deduce what it was doing, particularly since 
 it uses a lot of readregistry entries, and I don't know 
 what those do on Linux.  
 
  
 
 I also tried the verbose mode option, which tells me the 
 target framework is Mono 1.0 Profile, but that's not enough 
 info.  I've got a /usr/local/lib/mono/1.0 and a 
 /opt/mono-1.1.10/lib/mono/1.0 (I finally gave up with those 
 impossible-to-resolve mono rpm dependencies, and just ran the 
 installer).  I don't know what I'm supposed to set to get 
 NAnt to pick one versus the other.
 
  
 
 Help.  Thanks.
 
 - Kevin
 
  
 
 



---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] BUG Report

2005-11-15 Thread Gert Driesen
Aditya,

Please upgrade to a recent nightly build of NAnt
(http://nant.sourceforge.net/nightly/latest). Loads of issues with the
solution task were fixed after NAnt 0.84.

Thanks !

Gert
- Original Message - 
From: Aditya Patil [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Monday, October 31, 2005 9:23 PM
Subject: [nant-dev] BUG Report


Hi!

I am trying to build a web-based project and I am getting this particular
error.
 build-debug:

 [solution] Starting solution build.

[solution] Only C#, VB.NET http://VB.NET and C++ projects are
supported. Skipping
project 'flowViewPort

lSetup\flowViewPortalSetup.vdproj'.

[solution] Loading projects...

[solution] Loading project '
http://localhost/flowviewportal/FlowViewPortal.csproj'.

 onFailure:

 [echo] Error(s) occured in FlowViewPortal.csproj.

 BUILD FAILED

 INTERNAL ERROR

System.NullReferenceException: Object reference not set to an instance of an
object.

at NAnt.VSNet.Project.Load(Solution sln, String projectPath) in
c:\development\vssroot\development\framework1019

\resources\build\nant\nant-0.84\src\nant.vsnet\project.cs:line 221

at NAnt.VSNet.ProjectFactory.LoadProject(Solution sln, SolutionTask slnTask,
TempFileCollection tfc, String outp

utDir, String path) in
c:\development\vssroot\development\framework1019\resources\build\nant\nant-
0.84\src\nant.vsn

et\projectfactory.cs:line 70

at NAnt.VSNet.Solution.LoadProjects() in
c:\development\vssroot\development\framework1019\resources\build\nant\n

ant-0.84\src\nant.vsnet\solution.cs:line 407

at NAnt.VSNet.Solution..ctor(String solutionFileName, ArrayList
additionalProjects, ArrayList referenceProjects,

TempFileCollection tfc, SolutionTask solutionTask, WebMapCollection
webMappings, FileSet excludesProjects, String

outputDir) in
c:\development\vssroot\development\framework1019\resources\build\nant\nant-
0.84\src\nant.vsnet\soluti

on.cs:line 114

at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in
C:\Development\VSSROOT\Development\FRAMEWORK1019\Resources\Bui

ld\NAnt\nant-0.84\src\NAnt.VSNet\Tasks\SolutionTask.cs:line 317

at NAnt.Core.Task.Execute()

at NAnt.Core.Target.Execute()

at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)

at NAnt.Core.Tasks.CallTask.ExecuteTask()

at NAnt.Core.Task.Execute()

at NAnt.Core.Target.Execute()

at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)

at NAnt.Core.Project.Execute()

at NAnt.Core.Project.Run()

 Please send bug report to [EMAIL PROTECTED]


---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Help

2005-11-15 Thread Gert Driesen
Lizabeth,

This issue (and loads of other issues) was fixed since. Try using a recent
nightly build (http://nant.sourceforge.net/nightly/latest).

Gert

- Original Message - 
From: Raju, Lizabeth [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Tuesday, November 01, 2005 9:59 PM
Subject: [nant-dev] Help


I get this error during build. How can you help?

 Picture (Device Independent Bitmap)
 This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for
the addressee.  If you are not the intended recipient, do not use the
information in this e-mail in any way, delete this e-mail and notify the
sender. CEG-IP1


---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] entry point...

2005-11-14 Thread Gert Driesen

- Original Message - 
From: John Cole [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Monday, November 14, 2005 5:04 PM
Subject: [nant-dev] entry point...


 Hey guys,
   I'm trying to figure out how NAnt works :-) and I'm looking for where it
 loads the build file, and I can't seem to find it.  Could I get a pointer
 where to start looking?

NAnt.Core.ConsoleDriver

Let me know if you need more info.

Gert



---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Solution task feature proposal (with patch): write list of output s to a property

2005-10-30 Thread Gert Driesen
Hi Sean,

I like your idea, but I think we need to give it some more thought.

I think MSBuild also has something similar, but I haven't yet looked into
it. Anyone know more about what they use ?

I'd definitely prefer having something fileset-like instead of a simple
property to store the list of output files in.

Gert

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Foy, Sean
 Sent: zaterdag 29 oktober 2005 16:34
 To: 'nant-developers@lists.sourceforge.net'
 Subject: [nant-dev] Solution task feature proposal (with 
 patch): write list of output s to a property
 
 I'd like to be able to access a list of outputs generated by 
 the execution
 of the solution task. Attached is a patch that implements 
 this feature using
 NAnt properties. 
 
 The solution task now maintains a list of all outputs (and 
 also a list of
 just the assemblies it compiles) during its execution. Three 
 new optional
 properties provide access to this information:
 outputassembliesproperty -- Name of a property whose 
 value should be set
 to a list of assemblies produced during the execution of this task.
 outputfilesdelim -- String used to separate filenames for
 outputfilesproperty and outputassembliesproperty. : is the default.
 outputfilesproperty -- Name of a property whose value 
 should be set to a
 list of output files produced during the execution of this task.
 
 Here's an example use of the new feature:
 ---
 solution configuration=${configuration} 
 solutionfile=iDeal.sln
 failonerror=true verbose=${verboseP} 
 outputfilesproperty=outputFiles
 outputfilesdelim=: outputassembliesproperty=outputAssemblies
 assemblyfolders failonempty=true
 include name=${dependency-path}/** /
 /assemblyfolders
 /solution
 echo message=We could feed the following list to Ndepend: /
 foreach item=String in=${outputAssemblies} delim=:
 property=filename
 echo message=output: ${filename} /
 /foreach
 ---
 
 Comments, criticisms, suggestions?
 
 Sean Foy
 
 



---
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] internal error when using nunit.....

2005-10-15 Thread Gert Driesen
Dean,

This issue should indeed be fixed. Can you try using a recent nightly build
(http://nant.sourceforge.net/nightly/latest) ?

Gert 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Dean Hiller
 Sent: donderdag 13 oktober 2005 21:14
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] internal error when using nunit.
 
 Maybe this bug is already fixed.  If so, please let me know.  
 Otherwise, is there any way to work around this?
 
  
 
 I am using this version of ant
 
 NAnt 0.85 (Build 0.85.1869.0; rc2; 2/12/2005)
 
  
 
 It told me to email you this report..
 
 nunit:
 
  
 
  
 
 BUILD FAILED
 
  
 
 INTERNAL ERROR
 
  
 
 System.IO.FileNotFoundException: File or assembly name 
 nunit.core, or one of its
 
  dependencies, was not found.
 
 File name: nunit.core
 
at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask()
 
at NAnt.Core.Task.Execute()
 
at NAnt.Core.Target.Execute()
 
at NAnt.Core.Project.Execute(String targetName, Boolean 
 forceDependencies)
 
at NAnt.Core.Project.Execute()
 
at NAnt.Core.Project.Run()
 
  
 
 === Pre-bind state information ===
 
 LOG: DisplayName = nunit.core, Version=2.2.0.0, 
 Culture=neutral, PublicKeyToken=
 
 96d09a1eb7f44a77
 
  (Fully-specified)
 
 LOG: Appbase = 
 C:\AROOT\views\workviews\hsem40\common\framework\input\tools\nant
 
 \
 
 LOG: Initial PrivatePath = NULL
 
 Calling assembly : NAnt.NUnit2Tasks, Version=0.85.1869.0, 
 Culture=neutral, Publi
 
 cKeyToken=null.
 
 ===
 
  
 
 LOG: Private path hint found in configuration file: lib.
 
 LOG: Publisher policy file is not found.
 
 LOG: Host configuration file not found.
 
 LOG: Using machine configuration file from 
 C:\WINNT\Microsoft.NET\Framework\v1.1
 
 .4322\config\machine.config.
 
 LOG: Post-policy reference: nunit.core, Version=2.2.0.0, 
 Culture=neutral, Public
 
 KeyToken=96d09a1eb7f44a77
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/nunit.core.DLL.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/nunit.core/nunit.core.DLL.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/lib/nunit.core.DLL.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/lib/nunit.core/nunit.core.DLL.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/nunit.core.EXE.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/nunit.core/nunit.core.EXE.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/lib/nunit.core.EXE.
 
 LOG: Attempting download of new URL 
 file:///C:/AROOT/views/workviews/hsem40/comm
 
 on/framework/input/tools/nant/lib/nunit.core/nunit.core.EXE.
 
  
 
  
 
 Please send bug report to [EMAIL PROTECTED]
 
  
 
 Total time: 4.4 seconds.
 
 
 
 
 The information contained in this e-mail and any attachments 
 hereto are for the exclusive use of the addressee and may 
 contain confidential, privileged and nondisclosable 
 information. If the recipient of this e-mail is not the 
 addressee, or a person responsible for delivering this e-mail 
 to the addressee, such recipient is strictly prohibited from 
 reading, printing, photocopying, distributing or otherwise 
 using this e-mail or any attachments hereto in any way. If 
 the recipient has received this e-mail in error, please send 
 return e-mail immediately notifying us of your receipt of 
 this e-mail and delete the e-mail from your inbox. Thank you. 
 



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] VC++ compatibilty with NANT.

2005-10-12 Thread Gert Driesen
Kiran,

You need to make sure your PATH, INCLUDE and LIB environment variables are
set-up accordingly.

One way to do this is by executing vsvars32.bat (which is located in
Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools) first in
your DOS session.

Hope this helps,

Gert

- Original Message - 
From: ram kiran dhulipala [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Tuesday, October 11, 2005 2:17 PM
Subject: [nant-dev] VC++ compatibilty with NANT.



Hi ,
I am running NANT on a VC++ project.It is throwing an error as shown below..

Buildfile: file:///C:/1NET middleTier/N-Unit
test/NUnit/VCCONSOLETEST/VCCONSOLET
EST.build
Target framework: Microsoft .NET Framework 1.1
Target(s) specified: build


compile:

C:\1NET middleTier\N-Unit
test\NUnit\VCCONSOLETEST\VCCONSOLETEST.build(24,6): El
ement includes... / for fileset... / is deprecated. Use include
element in
stead.
   [cl] 'C:\debug\AssemblyInfo.obj' does not exist, recompiling.
   [cl] Compiling 3 files to 'C:\debug'.
   [cl] Contents of C:\DOCUME~1\X_UMAK~1\LOCALS~1\Temp\tmp722.tmp.
   [cl] /c
   [cl] $
   [cl] /FdC:\debug/
   [cl] /FoC:\debug/
   [cl] C:\1NET middleTier\N-Unit
test\NUnit\VCCONSOLETEST\AssemblyInfo.cpp

   [cl] C:\1NET middleTier\N-Unit test\NUnit\VCCONSOLETEST\stdafx.cpp
   [cl] C:\1NET middleTier\N-Unit
test\NUnit\VCCONSOLETEST\VCCONSOLETEST.cp
p
   [cl]
   [cl] Starting 'cl (@C:\DOCUME~1\X_UMAK~1\LOCALS~1\Temp\tmp722.tmp
/nolo
go)' in 'C:\1NET middleTier\N-Unit test\NUnit\VCCONSOLETEST'

BUILD FAILED - 0 non-fatal error(s), 1 warning(s)

C:\1NET middleTier\N-Unit
test\NUnit\VCCONSOLETEST\VCCONSOLETEST.build(23,6):
'cl' failed to start.
The system cannot find the file specified

Total time: 0.2 seconds.

Now i have started to suspect if there is a compatibility issue.Please help
me...

Regards
Kiran


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Bug report

2005-10-03 Thread Gert Driesen
Bertrand,

This should be fixed in cvs.

Can you try using a recent nightly build :

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

Gert

-Original Message-
From: Bertrand LEGA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 09:21 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Bug report

This message contains information that may be privileged or confidential and 
is the property of the Capgemini Group. It is intended only for the person to 
whom it is addressed. If you are not the intended recipient,  you are not 
authorized to read, print, retain, copy, disseminate,  distribute, or use this 
message or any part thereof. If you receive this  message in error, please 
notify the sender immediately and delete all  copies of this message.





---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] System.IO.FileLoadException

2005-10-03 Thread Gert Driesen
Hi Thormundur,

What version of NAnt are you using ?

Gert

-Original Message-
From: Þórmundur Helgason [mailto:[EMAIL PROTECTED]
Sent: Friday, September 16, 2005 01:32 PM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] System.IO.FileLoadException

See attachment



Regards,

Thormundur Helgason





Lýsing hf.



Kær kveðja / Best regards,
Þórmundur Helgason ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] )

Tölvunarfræðingur B.Sc.

Sérfræðingur í tölvudeild
Lýsing hf · Suðurlandsbraut 22 · 108 · Reykjavík · Iceland
Sími/tel: 540-1500 · 540-1563 gsm: 694-5496
www.lysing.is http://www.lysing.is



- fjármögnun í takt við þínar þarfir

  _

Efni þessa tölvupósts, sem og skjala og gagna sem send eru sem viðhengi, kann 
að vera trúnaðarmál og er eingöngu ætlað þeim sem tölvupósturinn er stílaður 
á.  Misnotkun getur varðað bótaábyrgð og refsingu, auk þess sem viðtakanda ber 
samkvæmt gildandi fjarskiptalögum að tilkynna sendanda hafi tölvupósturinn eða 
viðhengi hans ranglega borist honum.  Vinsamlegast eyðið tölvupóstinum og 
viðhengjum í slíkum tilvikum.  Efni tölvupóstsins og skjal og gagna sem send 
eru sem viðhengi er á ábyrgð sendanda ef það tengist ekki starfsemi Lýsingar 
hf.










---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] Re: suggestion: pause task

2005-10-03 Thread Gert Driesen

-Original Message-
From: Ynon Koralek [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 2, 2005 10:09 AM
To: [EMAIL PROTECTED]
Subject: suggestion: pause task

Hi!

I found it helpful to have a 'pause' task.

That simple task is similar to 'pause' command of CMD.

The task can be used remind the user something he should verify, and
then, press any key to continue...

The code is simple and includes comment property to contain the required
text.



What do you think?

I think we should implement something similar to Ant's input task 
(http://ant.apache.org/manual/CoreTasks/input.html) and its InputHandler 
framework (http://ant.apache.org/manual/inputhandler.html).

Gert




---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] filesets speed

2005-09-13 Thread Gert Driesen
Martin,

If you have time, please implement this optimization. However, as the
fileset implementation is a very critical feature of NAnt, any changes to it
should be accompanied by unit tests (and needless to say that all existing
tests should continue to pass).

Thanks !

Gert
- Original Message - 
From: Martin Aliger [EMAIL PROTECTED]
To: nant-developers@lists.sourceforge.net
Sent: Friday, September 09, 2005 5:37 PM
Subject: RE: [nant-dev] filesets speed



  c:\test\foo\etc should be discarded when scanned and not dip into, since
 none file/folder in it could ever satisfy any pattern.
  c:\test\foo\Gordic1 shouldn't be discarded and scanned normaly as today.
  c:\test\foo\Gordic1\_svn shouldn't be discarded as well
 ---^
 SHOULD BE. Since none file in this folder or subfolders could ever satisfy
 any pattern.


 Late friday and mine keyboard is tired or what :-)  Damn copy/paste!

 Regards,
 Martin




 ---
 SF.Net email is Sponsored by the Better Software Conference  EXPO
 September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
 Agile  Plan-Driven Development * Managing Projects  Teams * Testing  QA
 Security * Process Improvement  Measurement * http://www.sqe.com/bsce5sf
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers



---
SF.Net email is Sponsored by the Better Software Conference  EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile  Plan-Driven Development * Managing Projects  Teams * Testing  QA
Security * Process Improvement  Measurement * http://www.sqe.com/bsce5sf
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Fwd: Filesets referencing filesets ?

2005-09-08 Thread gert . driesen

-Original Message-
From: Martin Aliger [mailto:[EMAIL PROTECTED]
Sent: Monday, September 5, 2005 11:19 AM
To: nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] Fwd: Filesets referencing filesets ?

Hello,

 I agree, these problems should be resolved before we 
 introduce this feature.
 
  I'm tempted to include it and let people have a play with 
 it and then
  refine it as necessary rather than holding out until its 
 perfect. What
  do people think ?

I'm not convinced to either. Resolve those issues completely could be pretty
diffucult, but 95% use cases will be trivial case without basedirs and
include/exclude conflict. IMHO atleast overall strategy should be discussed
before introducing this feature to the core.
 
 I'd rather have a more general approach, where all global 
 types implement
 support for merging two distinct instances.

I dont think I catch it. How could have general type merge operator?

I'm pretty sure that merging several data type instances does not only apply to 
filesets.

For example, users will probably also want to have different sets of namespace 
imports that they can combine where needed.

I think you even made a proposal for this a while ago.

Gert




---
SF.Net email is Sponsored by the Better Software Conference  EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile  Plan-Driven Development * Managing Projects  Teams * Testing  QA
Security * Process Improvement  Measurement * http://www.sqe.com/bsce5sf
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


  1   2   3   4   5   6   7   8   >