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

[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 
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  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  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

[Gert Driesen]

Hey Martin,

I haven't had much time to review your patches yet, but here are a few
comments:

1) datetime_functions.patch

We now support overloaded functions, so I'd prefer this addition to be an
overload for to-string.
Problem is that we need to add support for overload in the doc generation.
I'm not yet sure what approach we need to take there.

2) element.patch

I understand the need, but we should avoid API changes.
Needs further discussion.

3) VSNet.patch

* ProjectBase.cs
change is ok to commit (although you may consider this an API change as
well).

* SolutionBase.cs
do you have an example where you needed this ?
the change is incomplete, as you don't need the try/catch in NET_2_0. 
If this change is necessary, then we need to refactor this out and apply it
to other code paths (even within SolutionBase).

4) vcprojs.patch
changes look ok, but would it be possible to provide a small VS project for
each change that fails without this patch ?

Thanks!

Gert

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

Hi NAnters,

looking into new 0.91 sources and I got there few patches locally which do
not make it into head yet. I hope I sent all of them to list (maybe some
only to Gert?).

Anyway - here are few minor ones (out of NAnt.MSBuild):

1) datetime_functions.patch
It just AIDS new function to allow datetime formatting (tostring with format
passed in)

2) element.patch
To support better error messages somewhere in Solution task I need to read
Location from non-descendant class. This allows read to public (write to
protected).

3) VSNet.patch
Adds VS2008 and VS2010. Plus minor change for Berger debugging on 2.0/4.

4) vcprojs
I'm no expert to C++ builds, but I got some code changes around to support
vcproj from VS2005 and VS2008 (need some work for VS2010).

Changes around: UsePrecompiledHeader, exception handling /EHS, managed
extenstions. Short changes, nothing big.


Martin Aliger

-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

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] Announcing NAnt 0.91 Alpha1

[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

[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  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 
>> 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

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

[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  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® 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® 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 

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

[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  wrote:


From: Richard Birkby 
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® 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

[Gert Driesen]

Hey Ryan,

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

Gert

--
From: "Ryan Boggs" 
Sent: Friday, March 26, 2010 3:53 PM
To: "Dominik Guder" 
Cc: 
Subject: Re: [nant-dev] sysinfo task

> Hi,
>
> On Mar 26, 2010, at 2:07 AM, Dominik Guder  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" >>>>> >
>>>>>> 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:
>>>>>>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>
>>>>>> 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  is kind of deprecated. So we
>> might not put to much effort into it.
>
> Does anyone know if  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® 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® 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® 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] property with parens (was sysinfo task)

[Gert Driesen]

Hey Dominik,

What version of NAnt are you running ?
I get a failure for the "foo(bar)" property:

Property name 'foo(bar)' is invalid.

Gert

-Original Message-
From: Dominik Guder [mailto:o...@guder.org] 
Sent: vrijdag 26 maart 2010 22:37
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] property with parens (was sysinfo task)

Am 26.03.2010 15:53, schrieb Ryan Boggs:
>> 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.








Result:
Build failed on last line with "Property 'foo' has not been set."
But I would expect that line one will fail where name of  task
is set to an invalid value.

So far Dominik


--
Download Intel® 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® 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

[Gert Driesen]

Hey Ryan,

Check the docs of the  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  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" >>>> >
>>>>> 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:
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>> 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  is kind of deprecated. So we
> might not put to much effort into it.

Does anyone know if  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® 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® 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® 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

[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.

Gert

--
From: "Ryan Boggs" 
Sent: Thursday, March 25, 2010 5:03 PM
To: "Gert Driesen" 
Cc: ; "Dominik Guder" 
Subject: Re: [nant-dev] sysinfo task

> Hi
>
> Ok, makes sense to me.  My only concern with this is the time table.
> Is it worth putting in 0.90 or should it target the future 1.0 release?
>
> Thanks,
> Ryan
>
> On Mar 25, 2010, at 8:54 AM, "Gert Driesen" 
> wrote:
>
>>
>>
>> ------
>> From: "Ryan Boggs" 
>> Sent: Thursday, March 25, 2010 4:45 PM
>> To: "Gert Driesen" 
>> Cc: ; "Dominik Guder" 
>> > >
>> Subject: Re: [nant-dev] sysinfo task
>>
>>> Hi,
>>>
>>> On Mar 25, 2010, at 8:10 AM, "Gert Driesen" 
>>> 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:
>>>
>>> 
>>>  
>>> 
>>>
>>> Am I understanding you right?
>>
>> Yes.
>>
>> Gert
>>
>
> --
> Download Intel® 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® 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

[Gert Driesen]

--
From: "Ryan Boggs" 
Sent: Thursday, March 25, 2010 4:45 PM
To: "Gert Driesen" 
Cc: ; "Dominik Guder" 
Subject: Re: [nant-dev] sysinfo task

> Hi,
>
> On Mar 25, 2010, at 8:10 AM, "Gert Driesen" 
> 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:
>
> 
>   
> 
>
> Am I understanding you right?

Yes.

Gert 



--
Download Intel® 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

[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" 
Sent: Thursday, March 25, 2010 3:59 PM
To: "Dominik Guder" 
Cc: 
Subject: Re: [nant-dev] sysinfo task

> Hi,
>
> On Mar 25, 2010, at 3:34 AM, Dominik Guder  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  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)
>> 
>> 
>> 
>> --- 
>> --- 
>> --- 
>> -
>> Download Intel® 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® 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® 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

[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: 
Subject: Re: [nant-dev] NAnt License

Het Gert,

On Mar 20, 2010, at 1:15 AM, "Gert Driesen"   
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® 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® 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

[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® 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.

[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" 
Sent: Wednesday, March 10, 2010 6:24 AM
To: 
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® 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® 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

[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 
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.
>
>  if="${platform.supports.registry}">
>        ...
> 
>
> 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.
>     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  wrote:
>
>> From: Ryan Boggs 
>> Subject: Re: [nant-dev] Task/planning for 0.87 release
>> To: "cchan...@users.sourceforge.net" 
>> Cc: "Gert Driesen" ,
> "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

--

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

[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® 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® 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

[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.


...


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.


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  wrote:

> From: Ryan Boggs 
> Subject: Re: [nant-dev] Task/planning for 0.87 release
> To: "cchan...@users.sourceforge.net" 
> Cc: "Gert Driesen" ,
"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® 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

[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  wrote:

> From: Ryan Boggs 
> 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® 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® 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?

[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® 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® 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?

[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" 
Sent: Thursday, February 25, 2010 4:20 AM
To: 
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® 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® 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]

[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 
To: Charles Chan ;
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]

[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 
> To: Charles Chan ;
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  task. Note,
however, we 

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

[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

[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" 
Sent: Thursday, February 11, 2010 4:23 AM
To: 
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

[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?

[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  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" 
Sent: Friday, June 12, 2009 10:58 AM
To: 
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?

[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" 
Sent: Friday, June 12, 2009 10:58 AM
To: 
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

[Gert Driesen]

Hi Manjusha,

No, this is not something we currently support in the  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

[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:


 
 
 
 
 


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

[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=100&url=/
___
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=100&url=/
___
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

[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
 &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=100&url=/___
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 programs

[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  programs

 

 

Hi,

 

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

 

My build file contains:





















 

And the output generated is:

  










Lots more warnings.

13296.7899

  

 

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  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=100&url=/___
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

[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 \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

[Gert Driesen]

Eric,
 
We do not yet support .NET Framework 3.5 for the  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:
 
  

 
  
 
  
  
 
  
  

  

  
 
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
 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

[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: .  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
 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)

[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: 
 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.7&r2=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.22&r2=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

[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: 
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

[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

[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:


   
 
   http://schemas.microsoft.com/developer/msbuild/2003"; />
 
   
 

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

[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:
 


 








 












 
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  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:
 




























...


 
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

[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:
 


 








 











 
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  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:
 



























...

 
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? task doesn't work as expected when calledwithin a nant.onsuccess target

[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?  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  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  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
 the build if a non-fatal error was detected.

http://nant.sf.net/nant-all.xsd";>




 



















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
 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

[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 , , , ...
* Several bug fixes.
 
Types
* Case-sensitivity fixes for .

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?

[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

[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.php&p=sourceforge&CID=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

[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  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.236&r2=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.
>

[nant-dev]

[Gert Driesen]

Hi Jay (or anyone else with an opinion on this),

Few small questions: 

I'm adding a first version of a  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=lnk&kid=120709&bid=263057&dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

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

[Gert Driesen]

> -Original Message-
> From: Martin Aliger [mailto:[EMAIL PROTECTED]
> Sent: donderdag 21 december 2006 16:36
> To: 'Abhilash Panickar'; 'Gert Driesen'
> Cc: nant-developers@lists.sourceforge.net
> Subject: RE: [nant-dev] Building VS2005 projects using NANT 8.5 rc4
> 
> The code is in place, I personally am using it in the production, but
> there
> was no official release of this feature yet. We are missing testcases,
> documentation at all. Not all parts of code passed the project
> administrator
> review so far.
> 
> Gert - how you see the patches now?

I've been working on it for a few hours now, and it's progressing nicely.
I'll probably have a little more time later, so I might get it committed
today.

For now, I've reverted it back to a flat directory structure, reduced the
public exposure of classes and made a few modifications to both NAnt.Core
and NAnt.VSNet to remove the need for a list of consumers (in PluginScanner)
and register plugins in TaskBuilder.CreateTask.

I will not yet enable the CustomProperties on SolutionTask. This needs more
discussion first.

Also, do you think we should move WhidbeySolutionProvider (and
WhidbeySolution) to NAnt.MSBuild ?

Are we planning to support multiple versions of MSBuild in NAnt.MSBuild (by
using a reflection-based API) ?

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.php&p=sourceforge&CID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] .Net 2.0 Task dlls

[Gert Driesen]

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nant-
> [EMAIL PROTECTED] On Behalf Of Tony McCreath
> Sent: donderdag 9 november 2006 0:42
> To: nant-developers@lists.sourceforge.net
> Subject: [nant-dev] .Net 2.0 Task dlls
> 
> I've just upgraded to .Net 2.0 and in the process converted my NAnt
> tasks.
> 
> However, NAnt (0.85) cannot read these tasks once compiled into .Net
> 2.0!
> 
> I am specifying -t:net-2.0
> 
> using something like:
> 
> 
> I get:
> 
> BUILD FAILED
> C:\Documents and Settings\Tony McCreath\My Documents\Visual Studio
> Projects\Nexus\Storm2_1\Nexus.Storm.Build\Release.WebSite.build(23,4):
> Failure scanning \"C:\Documents and Settings\Tony McCreath\My
> Documents\Visual Studio
> Projects\Nexus\Storm2_1\Nexus.Storm.Build\Assemblies\Nexus.NAnt.Tasks.d
> ll\"
> for extensions.
> The format of the file 'Nexus.NAnt.Tasks.dll' is invalid.

Changing the target framework (using -t or using the
nant.settings.currentframework property) does not affect the CLR in which
NAnt is running.

The NAnt binaries that are shipped in the distribution packages are built
targeting .NET 1.0, and would therefor prefer to run on the .NET Framework
1.0 (unless it's not installed).

However, we ship NAnt with an application configuration file
(NAnt.exe.config) in which we force NAnt to run on the latest available CLR
(.NET 2.0 / Mono 2.0) if available.

This is done using the  elements in the  node.

Now, on to your issue: 

* have you manually modified NAnt.exe.config, and removed some elements from
the  node ?
* do you have .NET 2.0 installed on the system on which you're trying to
load the .NET 2.0-built task assembly ?
* are you allowed to share the task assembly in question ?

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=lnk&kid=120709&bid=263057&dat=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?

[Gert Driesen]

Paul,

The  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  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
> ==
> 
>xmlns="http://nant.sf.net/release/0.85/nant.xsd";>
> 
>   
>   
> 
>   
>   
>   
> 
>   
>  solutionfile="${solution.dir}\ClassLibrary1.sln"
>   outputdir="build\debug">
>   
>   
> 
>   
>   
>   
>   
>   
>   
> 
> 
> ---
> --
> 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=lnk&kid=120709&bid=263057&dat=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=lnk&kid=120709&bid=263057&dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] aspnet_compiler task

[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]>; 
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,



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 



> 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,> > > >





> -
> 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=lnk&kid=120709&bid=263057&dat=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=lnk&kid=120709&bid=263057&dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] aspnet_compiler task

[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 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 stuff

Thanks for clarifying it
 











> 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,
> 
> 
> 
> 








-
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=lnk&kid=120709&bid=263057&dat=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

[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=lnk&kid=120709&bid=263057&dat=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

[Gert Driesen]

- Original Message - 
From: "Ryan Baxter" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: 
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  section, but still had
> the same compile errors.  Confused.  Thanks for the response.

With csc I meant the  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: 
>> 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:
>> >
>> > 
>> >
>> >> > verbose="true">
>> >  
>> >
>> >  
>> >  
>> >
>> >  
>> >  
>> >
>> >
>> >
>> >  
>> >
>> >  
>> >
>> > 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

Re: [nant-dev] Csc Task Ignoring References

[Gert Driesen]

Ryan,

In that case, csc cannot locate the referenced assemblies.

Gert
- Original Message - 
From: "Ryan Baxter" <[EMAIL PROTECTED]>
To: 
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:
>
> 
>
>
>  
>
>  
>  
>
>  
>  
>
>
>
>  
>
>  
>
> 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=lnk&kid=120709&bid=263057&dat=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=lnk&kid=120709&bid=263057&dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

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

[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,









-
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=lnk&kid=120709&bid=263057&dat=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 in

[Gert Driesen]

Amish,

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

Gert

- Original Message - 
From: "amish" <[EMAIL PROTECTED]>
To: 
Sent: Monday, September 18, 2006 9:19 AM
Subject: [nant-dev] Problem in add reference of the other project 
in


> 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=lnk&kid=120709&bid=263057&dat=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=lnk&kid=120709&bid=263057&dat=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...

[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  task on a build files
> that have a  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:
> 
>