[nant-dev] New Pull Requests

[Ryan Boggs]

Hi all,

I have a couple of pull requests for NAnt over at github.com that I am
hoping to get some more eyes on before they go in.  The links are below.
So if any of you that have a moment and a github.com account, would you
mind taking a look and let me know if any changes need to be made?

This one addresses issues #108 and #110 where the task is still evaluated
even though the if attribute returns false. Which can cause problems.
https://github.com/nant/nant/pull/133

This one addresses issue #84 where 'null' property values are sneaking in
with the foreach task.
https://github.com/nant/nant/pull/134

Looking forward to hearing something

Thanks,
Ryan
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] New Nightlys Available

[Ryan Boggs]

Hi,

I just wanted to let people know that a new nightly builds have been
posted at sourceforge.net.  The links are below.

http://sourceforge.net/projects/nant/files/nant/nightly/2014-12-22/
http://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/2014-12-22/

This build addresses the following items:

 * Fixes issues with the  task that was introduced in 0.92
 * Adds initial implementation of parallel execution
 * The net-2.0 target now uses the Windows SDKs by default instead of
the old .NET 2.0 sdk.
- NAnt will fallback to the old .NET 2.0 sdk if no valid Windows
SDKs are found on the running machine.

We encourage the users to give this nightly build a try to see what
else they would like added/modified/fixed that have not already been
reported in NAnt's issues page on github.com.

https://github.com/nant

We'll send out updates as they come in.

You can also see commits to both NAnt/NAntContrib projects on twitter:
https://twitter.com/nantproject

Happy holidays. :)

Thanks,
Ryan

--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Adding an update parameter to the task

[Ryan Boggs]

Hi,

Before anything is done with dotnetzip, can someone with better license 
knowledge than me chime in regarding compatibility between gplv2 and ms-pl?  I 
don't mind upgrading libs when applicable but I don't want to get into issues 
regarding lib licenses.

Hope that makes sense.

Thanks,
Ryan

On Dec 13, 2012, at 3:04 PM, Leszek Ciesielski  wrote:

> Jerome,
> 
> I don't suppose you could also re-write the code to use DotNetZip
> instead of SharpZipLib? :-) The reason I'm mentioning this is because
> 1) DotNetZip is maintained, and SharpZipLib no longer seems to be
> 2) DotNetZip supports multithreaded zip compression, which is a huge
> gain for practically any machine now
> 
> Binary reference .dll size is 200k (Reduced, i.e. no self-extracting
> archive creation support), so the same as SharpZipLib that NAnt
> currently ships with.
> 
> On Thu, Dec 13, 2012 at 3:06 PM, Ryan Boggs  wrote:
>> Sorry, forgot to CC list.
>> 
>> Thanks,
>> Ryan
>> 
>> -- Forwarded message --
>> From: Ryan Boggs 
>> Date: Thu, Dec 13, 2012 at 7:04 AM
>> Subject: Re: [nant-dev] Adding an update parameter to the  task
>> To: jerome.duc...@solog.net
>> 
>> 
>> Hi Jerome,
>> 
>> If you don't mind, could you please open up a pull request via github
>> with this change?  It's easier for us (me at least) to review
>> contributions this way.
>> 
>> NAnt/NAntContrib Dev Guide:
>> https://github.com/nant/nant/wiki/Development-Guide
>> 
>> Github Pull Request Guide:
>> https://help.github.com/articles/using-pull-requests
>> 
>> Thanks,
>> Ryan
>> 
>> On Thu, Dec 13, 2012 at 5:32 AM,   wrote:
>>> Attached is a first draft of a
>>> https://github.com/nant/nant/tree/master/src/NAnt.Compression/Tasks/ZipTask.cs
>>> version allowing to append files to an existing zip archive (see
>>> http://ant.apache.org/manual/Tasks/zip.html).
>>> Is it worth writing a unit test for it? What do you think?
>>> /J
>>> 
>>> --
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> ___
>>> nant-developers mailing list
>>> nant-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/nant-developers
>> 
>> --
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> ___
>> nant-developers mailing list
>> nant-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nant-developers

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Adding an update parameter to the task

[Ryan Boggs]

Sorry, forgot to CC list.

Thanks,
Ryan

-- Forwarded message --
From: Ryan Boggs 
Date: Thu, Dec 13, 2012 at 7:04 AM
Subject: Re: [nant-dev] Adding an update parameter to the  task
To: jerome.duc...@solog.net


Hi Jerome,

If you don't mind, could you please open up a pull request via github
with this change?  It's easier for us (me at least) to review
contributions this way.

NAnt/NAntContrib Dev Guide:
https://github.com/nant/nant/wiki/Development-Guide

Github Pull Request Guide:
https://help.github.com/articles/using-pull-requests

Thanks,
Ryan

On Thu, Dec 13, 2012 at 5:32 AM,   wrote:
> Attached is a first draft of a
> https://github.com/nant/nant/tree/master/src/NAnt.Compression/Tasks/ZipTask.cs
> version allowing to append files to an existing zip archive (see
> http://ant.apache.org/manual/Tasks/zip.html).
> Is it worth writing a unit test for it? What do you think?
> /J
>
> --
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] regression in 0.92

[Ryan Boggs]

Hi Leszek,

To my knowledge, this is not a known issue.  Would you mind reporting
it in NAnt's issues list please?  I don't want this issue getting lost
in my email.

https://github.com/nant/nant/issues

Thanks,
Ryan

On Wed, Jun 27, 2012 at 9:51 AM, Leszek Ciesielski  wrote:
> Hi everyone,
>
> it seems that the  task has regressed, throwing an exception when
> only 'unless' condition is defined on it. It's simple to workaround
> (just use test="${not (unlessCondition)}" instead ), but annoying none
> the less. What's more, the task parsing exception thrown does not
> contain any line/location information (it's cut off after "at :"). Is
> this a known issue?
>
> Kind regards,
>
> Leszek 'skolima' Ciesielski
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ANN] Announcing NAnt/NAntContrib 0.92 Final Release

[Ryan Boggs]

We are proud to announce the final release of NAnt/NAntContrib 0.92.

This release focuses on fixing issues on both projects while
introducing new features that we feel add greater flexibility and
performance.  Details of these changes may be found in the release
notes of each project's homepage.

Binary and source distributions are available for immediate download from:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.92/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.92/

The GIT tag for NAnt/NAntContrib 0.92 Release is:
rel-0-92

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

For those who would like to contribute, please see the
NAnt/NAntContrib Develoment guide which can be found here:
https://github.com/nant/nant/wiki/Development-Guide

Bugs can be reported using Github.com's issue tracker at:
NAnt:
https://github.com/nant/nant/issues

NAntContrib:
https://github.com/nant/nantcontrib/issues

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

NAnt/NAntContrib is now on twitter.  Check here for announcements and
the latest github.com commits for each project:
https://twitter.com/#!/nantproject

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.
https://github.com/nant/nant

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.
Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.
https://github.com/nant/nantcontrib

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Fwd: CLR4/CLR2 NUnit binding

[Ryan Boggs]

Hi,

That's because the nunit2 is running on the framework that NAnt is
currently running on.  Which is the highest version of the .NET
framework found on your machine.  I see that you have two options.

1) Compile your project on 4.0
or
2) If you must compile your project on 3.5, then you could edit the
NAnt.exe.config to not run on 4.0 by removing/commenting out the
element listed below at the bottom of the file.  Please be advised
that this may also have unforeseen side-effects when running NAnt.
Thus, I do not recommend this course of action.

Xml Element to delete/comment in NAnt.exe.config:


Hope this info is helpful.

Thanks,
Ryan

On Fri, Jun 1, 2012 at 3:16 AM, Richard Birkby  wrote:
> Hi
>
> I didn't get a reply to this question on nant-users.
> I want my nant script to run NUnit () under .Net 3.5 - it runs
> everything else (eg ) correctly when I specify a target framework
> of net-3.5.
> But NUnit seems to be run as .Net 4 and consequently I get the following
> errors:
>
>    [nunit2] Test Fixture SetUp Failures:
>    [nunit2] 1) AlerterTests : SetUp : System.IO.FileLoadException : Mixed
> mode assembly is built against version 'v2.0.50727' of the runtime and
> cannot be loaded in the 4.0 run...
>    [nunit2] at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly
> assembly, String name, Boolean throwOnError, Boolean ignoreCase,
> ObjectHandleOnStack type)
>    [nunit2] at System.Reflection.RuntimeAssembly.GetType(String name,
> Boolean throwOnError, Boolean ignoreCase)
>    [nunit2] at System.Reflection.Assembly.GetType(String name, Boolean
> throwOnError)
>    [nunit2] at
> Microsoft.SqlServer.Management.Common.ServerConnection.GetStatements(String
> query, ExecutionTypes executionType, Int32& statementsToReverse)
>    [nunit2] at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
> sqlCommand, ExecutionTypes executionType)
>
>
> I still get this problem with 0.92rc1. What can I do about it?
> Is this because  is run as a different process, whereas  is
> run in the same process as Nant?
>
>
> Thanks,
> Richard
>
>
> -- Forwarded message --
> From: Richard Birkby 
> Date: Mon, Oct 24, 2011 at 9:51 AM
> Subject: CLR4/CLR2 NUnit binding
> To: nant-us...@lists.sourceforge.net
>
>
> Hi,
>
> I've tried to upgrade our Nant 0.90 to Nant 0.91 this morning. Everything
> went well apart from the test phase where NUnit failed with errors such as:
>
>  : System.IO.FileLoadException : Mixed mode assembly is built against
> version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime
> without additional configuration information.
>
> It appears from ildasm that Nant correctly built my assemblies against .Net
> 3.5, however when it starts running the nunit2 task, it thinks it should run
> it as .Net 4.
>
> What should I do to tell it to run it as .Net 3.5?
>
>
> Thanks,
> Richard
> ps There is a small possibility I corrupted the merge of Nant 0.91 into the
> existing structure. Could this be the reason?
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt/NAntContrib development guide

[Ryan Boggs]

Hi,

I have received a few emails over the last few months on contributing
to either the NAnt or NAntContrib projects, which I am happy to see.
So rather than answering everyone individually, I figured I would just
compose one email and send it to the lists.  For those of you who wish
to contribute to either project, there is a wiki page that describes,
in detail, how you can contribute and what you need to do in order to
submit your code.  If you have any suggestions or changes for this
document, please feel free to contact us to let us know how we can
improve on this document.

https://github.com/nant/nant/wiki/Development-Guide

Thanks,
Ryan

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ANN] Announcing NAnt/NAntContrib 0.92 Release Candidate 1

[Ryan Boggs]

We are proud to announce the final release of NAnt/NAntContrib 0.92
Release Candidate 1.

This release focuses on fixing issues on both projects while
introducing new features that we feel add greater flexibility and
performance.  Details of these changes may be found in the release
notes of each project's homepage.

Binary and source distributions are available for immediate download from:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.92-rc1/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.92-rc1/

The GIT tag for NAnt/NAntContrib 0.92 Release Candidate 1 is:
rel-0-92-rc1

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

For those who would like to contribute, please see the
NAnt/NAntContrib Develoment guide which can be found here:
https://github.com/nant/nant/wiki/Development-Guide

Bugs can be reported using Github.com's issue tracker at:
NAnt:
https://github.com/nant/nant/issues

NAntContrib:
https://github.com/nant/nantcontrib/issues

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

NAnt/NAntContrib is now on twitter.  Check here for announcements and
the latest github.com commits for each project:
https://twitter.com/#!/nantproject

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.
https://github.com/nant/nant

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.
Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.
https://github.com/nant/nantcontrib

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt/NAntContrib 0.92 RC1 Delay

[Ryan Boggs]

Hi,

Just wanted to give everyone a heads up.  The 0.92 release candidate 1
release will be delayed slightly.  It was suppose to be released this
weekend but given that I had little time this weekend and there was
quite a bit of changes today, I thought a slight delay would be in
order.  I plan on performing the RC1 release for both NAnt and
NAntContrib by this coming Wednesday (5/23/2012).  The estimated
release date for 0.92 final has not changed.

Sorry for the inconvenience this may have caused.

Thanks,
Ryan

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Heads Up: Breaking Change to XmlPokeTask

[Ryan Boggs]

Hi,

Just wanting to let everyone know that a breaking change has been
introduced to the XmlPokeTask.  Now, if XmlPoke does not find the
specified XPath location in the target xml file, the task will throw
an error.  This was done to make XmlPoke honor the "failonerror"
attribute.  If you want to old behavior, simply set the "failonerror"
attribute to "false."

Thanks,
Ryan

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ANN] Announcing NAnt/NAntContrib 0.92 Beta1

[Ryan Boggs]

We are proud to announce the release of NAnt/NAntContrib 0.92 Beta1.

Both NAnt and NAntContrib source code is now housed on Github.com.
NAnt's github.com home page for both NAnt and NAntContrib can be found
at https://github.com/nant.  While current and future development will
occur at github.com, the existing SF.net project pages will continue
to host all of the release and nightly builds.

This release focuses on fixing issues on both projects while
introducing new features that we feel add greater flexibility and
performance.  Details of these changes may be found in the release
notes of each project's homepage.

Binary and source distributions are available for immediate download from:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.92-beta1/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.92-beta1/

The GIT tag for NAnt/NAntContrib 0.92 Beta1 is:
rel-0-92-beta1

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

For those who would like to contribute, please see the
NAnt/NAntContrib Develoment guide which can be found here:
https://github.com/nant/nant/wiki/Development-Guide

Bugs can be reported using Github.com's issue tracker at:
NAnt:
https://github.com/nant/nant/issues

NAntContrib:
https://github.com/nant/nantcontrib/issues

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

NAnt/NAntContrib is now on twitter.  Check here for announcements and
the latest github.com commits for each project:
https://twitter.com/#!/nantproject

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.
https://github.com/nant/nant

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.
Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.
https://github.com/nant/nantcontrib

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ANN] Announcing NAnt/NAntContrib 0.92 Alpha1

[Ryan Boggs]

We are proud to announce the final release of NAnt/NAntContrib 0.92 Alpha1.

This marks the first release since the NAnt project relocated its
repos to github.com.  NAnt's github.com home page for both NAnt and
NAntContrib can be found at https://github.com/nant.  While current
and future development will occur at github.com, the existing SF.net
project pages will continue to host all of the release and nightly
builds.

This release focuses on fixing issues on both projects while
introducing new features that we feel add greater flexibility and
performance.  Details of these changes may be found in the release
notes of each project's homepage.

Binary and source distributions are available for immediate download from:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.92-alpha1/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.92-alpha1/

The GIT tag for NAnt/NAntContrib 0.92 Alpha1 is:
rel-0-92-alpha1

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

For those who would like to contribute, please see the
NAnt/NAntContrib Develoment guide which can be found here:
https://github.com/nant/nant/wiki/Development-Guide

Bugs can be reported using Github.com's issue tracker at:
NAnt:
https://github.com/nant/nant/issues

NAntContrib:
https://github.com/nant/nantcontrib/issues

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

NAnt/NAntContrib is now on twitter.  Check here for announcements and
the latest github.com commits for each project:
https://twitter.com/#!/nantproject

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.
https://github.com/nant/nant

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.
Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.
https://github.com/nant/nantcontrib

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] NAnt/NAntContrib 0.92 tentative release schedule

[Ryan Boggs]

Hi,

Just wanted to give everyone a heads up.  The release schedule has
been pushed out a week to try to get a couple more updates in before
the first alpha is out the door, which will now be next weekend (April
21/22).  Sorry for the inconvenience this may have caused.

Thanks,
Ryan

On Wed, Mar 21, 2012 at 5:11 PM, Ryan Boggs  wrote:
> Hi all,
>
> There's been quite a bit of developments these past months in the NAnt
> projects, as many of you may know, and now I think we are at a point
> to start up the release process for 0.92.  The current plan is to
> perform the first 0.92 alpha release for both NAnt and NAntContrib
> around the weekend of April 14th/15th 2012 and then perform another
> release every two weeks after that until 0.92 final is out the door.
> I'm hoping that the next few weeks will allow us to get in a few more
> updates before the first 0.92 alpha is out the door.  I will be
> setting up milestones in the appropriate projects in github to help
> illustrate the release time lines as they are updated.
>
> So that is the plan.  If anyone has suggestions/comments, please feel
> free to let us know.
>
> Thanks,
> Ryan

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt/NAntContrib 0.92 tentative release schedule

[Ryan Boggs]

Hi all,

There's been quite a bit of developments these past months in the NAnt
projects, as many of you may know, and now I think we are at a point
to start up the release process for 0.92.  The current plan is to
perform the first 0.92 alpha release for both NAnt and NAntContrib
around the weekend of April 14th/15th 2012 and then perform another
release every two weeks after that until 0.92 final is out the door.
I'm hoping that the next few weeks will allow us to get in a few more
updates before the first 0.92 alpha is out the door.  I will be
setting up milestones in the appropriate projects in github to help
illustrate the release time lines as they are updated.

So that is the plan.  If anyone has suggestions/comments, please feel
free to let us know.

Thanks,
Ryan

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Copy/Move directory fix

[Ryan Boggs]

Hi,

Just a quick update, I made some additional adjustments to this fix
based on some feedback I have received and updated the pull request
link below.  I'm CCing the user list just in case there are people in
here that are interested in reviewing this change.  Feel free to
provide any feedback to the pull request if you have any
comments/thoughts.

Thanks,

On Thu, Mar 15, 2012 at 8:32 PM, Ryan Boggs  wrote:
> Hi,
>
> I just created a pull request to fix the issues regarding
> moving/copying directories.  The link is below.  If anyone interested
> in getting this fix in to master, please take a look at the diffs in
> question and see if they look ok.  Feel free to leave any relevant
> comments on the pull request.
>
> https://github.com/nant/nant/pull/39
>
> Thanks in advance,
> Ryan

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Copy/Move directory fix

[Ryan Boggs]

Hi,

I just created a pull request to fix the issues regarding
moving/copying directories.  The link is below.  If anyone interested
in getting this fix in to master, please take a look at the diffs in
question and see if they look ok.  Feel free to leave any relevant
comments on the pull request.

https://github.com/nant/nant/pull/39

Thanks in advance,
Ryan

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Latest Nightly Build

[Ryan Boggs]

Hi,

Just another FYI -
The latest nightly build (2012-03-02) for NAnt contains the latest
changes to the  task (ie: updates the nunit2 libs to version
2.6).  For those interested, please test.
https://sourceforge.net/projects/nant/files/nant/nightly/2012-03-02/

Thanks,
Ryan

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] NUnit Updates Merge Scheduled

[Ryan Boggs]

Update: NAnt now references NUnit version 2.6 in master.  A new
nightly build is scheduled for tomorrow with these changes.

Please note: Since the changes have been merged to master, the
nunitupdates branch that this work originated from has been removed.

Thanks,
Ryan

On Thu, Mar 1, 2012 at 2:43 PM, Ryan Boggs  wrote:
> Hi all,
>
> Just an FYI, I'm planning on merging updates to the nunit2 task to the
> master branch within the next few hours.  These updates will bring
> NAnt's NUnit2 reference libs from version 2.2 to 2.6.0.  Once this
> goes in, a new nightly should be available the following 24 hours in
> the usual place in sourceforge.net.
>
> Thanks,
> Ryan

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NUnit Updates Merge Scheduled

[Ryan Boggs]

Hi all,

Just an FYI, I'm planning on merging updates to the nunit2 task to the
master branch within the next few hours.  These updates will bring
NAnt's NUnit2 reference libs from version 2.2 to 2.6.0.  Once this
goes in, a new nightly should be available the following 24 hours in
the usual place in sourceforge.net.

Thanks,
Ryan

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Various NAnt Updates

[Ryan Boggs]

Hi,

On Wed, Feb 22, 2012 at 11:46 PM, Richard Birkby  wrote:
> Sounds great. Looking forward to it.
>
> For me, the big omission from the current nunit task has been /label
> support so I can figure out which failing test produced the exceptions
> in our 2MB of test/build output.
>
> I have had a look at the branch, but it doesn't look like it supports
> /label. Is that correct?
Yeah, I was more worried about getting the new version of NUnit
working with NAnt than adding features.  However, I just took a look
in NUnit's console setup for the label argument.  Implementing this
seems pretty easy enough and the impact on how the task runs is
minimal.  Just need to make sure it looks ok when it is printed.  I'll
see about adding this today.  Thanks for the tip. :)
>
> Additionally, while I don't use the style task, I notice you aren't caching
> the compiled XSL transform between runs. This means you will incur a compile
> on every invocation. This will kill performance for users transforming many
> files.
Hmm, good observation.  I'll take a look and see what's needed to get
the caching going for this task.

Thanks,
Ryan
>
>
> Richard
>
> On Thu, Feb 23, 2012 at 4:31 AM, Ryan Boggs  wrote:
>>
>> Hi all,
>>
>> Just checking in with some progress that has been occurring in NAnt's
>> development.  It's not a complete list but there are a few big ones
>> that I think are worth highlighting.
>>
>> * The VS project solution files for both NAnt and NAntContrib projects
>> have been updated to VS2010 format.
>>
>> * .NET/Mono 1.* runtime support for NAnt has been dropped.  Target
>> support for .NET/Mono 1.* still exists, however.
>>
>> * The  task has been updated to use xslCompiledTransform,
>> which should address the issue described here on Stackoverflow:
>>
>> http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-closing-tags-with-empty-paired-tags
>> Thanks to Michael Tutty for the contribution via pull request for this
>> item.
>>
>> * The  task has been updated to use System.Net.Mail instead of
>> System.Web.Mail.  During the process of updating this task, additional
>> features were added that we thought to be very helpful (such as
>> specifying a reply to address, specifying the port number to send mail
>> to, indicating whether or not to use an ssl connection, etc).
>>
>> * More work has gone into the  with the help from Dominik
>> Guder and Martin Aliger.  From what I understand, there are still a
>> couple of outstanding issues with this item but the task is working
>> better with recent versions of msbuild scripts.  This is still a high
>> priority.
>>
>> * Quite a bit of work has been put into upgrading the  task
>> to reference the latest version of NUnit.  I'm happy to say that these
>> changes are currently in review to be imported into nant/master.  The
>> version of NUnit being used for this upgrade is 2.6 final (which was
>> released just a few days ago).  I'm hoping that this will go into
>> master soon.  I want to say thanks to Charles Poole and the rest of
>> the NUnit dev team for their help and insight to get the  up
>> to speed.  They were very helpful in this process.  Anyone interested
>> in viewing these changes can see them here:
>> https://github.com/nant/nant/tree/nunitupdates
>>
>> * The nightly process for both NAnt and NAntContrib projects have
>> started up again.  This time, an automated process has been setup with
>> extensive help from Dominik Guder to make sure that new nightly files
>> are generated whenever changes occur on the master branches of either
>> project.  The last nightly was built on 2/19/2012 and includes all the
>> changes listed above except for the nunit changes.  The nightly files
>> can be found in the following locations:
>> NAnt Nightlys:
>> https://sourceforge.net/projects/nant/files/nant/nightly/
>>
>> NAntContrib Nightlys:
>> https://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/
>>
>> We are still trying to nail down release dates and should be
>> announcing them as soon as they are finalized.
>>
>> The next version number being targeted for NAnt/NAntContrib is
>> currently 0.92. It seems like the natural progression but we are
>> curious if you have any reasons to use a different version number (ie:
>> should we skip 0.92 and go to 0.95, etc).
>>
>> That's all I have for now.  I will try to send out these kinds of
>> notices more often as progress continues.
>>
>> Thanks,
>> Ry

Re: [nant-dev] [NAnt-users] Various NAnt Updates

[Ryan Boggs]

Hi,

On Thu, Feb 23, 2012 at 6:53 AM, Bob Archer  wrote:
> Looks like some good changes.
>
> Is the nunit stuff going to be version specific? Or, is it chaining out to 
> whatever version of nunit you have or point to in your project?
I am hoping that people using a certain version of NUnit for their
tasks will not have to touch their setup but if anyone wants to use
features from the latest NUnit version, they will be able to through
the NAnt task.
>
> You might want to update the readme with the versions that are supported:
There is no "might" about it.  The readme needs updating. :)

Thanks,
Ryan
>
>   Windows
>   ---
>
>       * A version of the Microsoft .NET Framework
>
>           Available from http://msdn.microsoft.com/netframework/
>
>           You will need the .NET Framework SDK as well as the runtime
>           components if you intend to compile programs.
>
>           Note: NAnt currently supports versions 1.0, 1.1 and 2.0
>           of the Microsoft .NET Framework.
>
>       or
>
>       * Mono for Windows (version 1.0 or higher)
>
>           Available from http://www.mono-project.com/downloads/
>
> BOb
>
>
>> -Original Message-
>> From: Ryan Boggs [mailto:rmbo...@gmail.com]
>> Sent: Wednesday, February 22, 2012 11:31 PM
>> To: nant-developers@lists.sourceforge.net; nant-us...@lists.sourceforge.net
>> Subject: [NAnt-users] Various NAnt Updates
>>
>> Hi all,
>>
>> Just checking in with some progress that has been occurring in NAnt's
>> development.  It's not a complete list but there are a few big ones that I 
>> think
>> are worth highlighting.
>>
>> * The VS project solution files for both NAnt and NAntContrib projects have
>> been updated to VS2010 format.
>>
>> * .NET/Mono 1.* runtime support for NAnt has been dropped.  Target support
>> for .NET/Mono 1.* still exists, however.
>>
>> * The  task has been updated to use xslCompiledTransform, which
>> should address the issue described here on Stackoverflow:
>> http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-
>> closing-tags-with-empty-paired-tags
>> Thanks to Michael Tutty for the contribution via pull request for this item.
>>
>> * The  task has been updated to use System.Net.Mail instead of
>> System.Web.Mail.  During the process of updating this task, additional 
>> features
>> were added that we thought to be very helpful (such as specifying a reply to
>> address, specifying the port number to send mail to, indicating whether or 
>> not
>> to use an ssl connection, etc).
>>
>> * More work has gone into the  with the help from Dominik Guder
>> and Martin Aliger.  From what I understand, there are still a couple of
>> outstanding issues with this item but the task is working better with recent
>> versions of msbuild scripts.  This is still a high priority.
>>
>> * Quite a bit of work has been put into upgrading the  task to
>> reference the latest version of NUnit.  I'm happy to say that these changes 
>> are
>> currently in review to be imported into nant/master.  The version of NUnit
>> being used for this upgrade is 2.6 final (which was released just a few days
>> ago).  I'm hoping that this will go into master soon.  I want to say thanks 
>> to
>> Charles Poole and the rest of the NUnit dev team for their help and insight 
>> to
>> get the  up to speed.  They were very helpful in this process.  
>> Anyone
>> interested in viewing these changes can see them here:
>> https://github.com/nant/nant/tree/nunitupdates
>>
>> * The nightly process for both NAnt and NAntContrib projects have started up
>> again.  This time, an automated process has been setup with extensive help
>> from Dominik Guder to make sure that new nightly files are generated
>> whenever changes occur on the master branches of either project.  The last
>> nightly was built on 2/19/2012 and includes all the changes listed above 
>> except
>> for the nunit changes.  The nightly files can be found in the following 
>> locations:
>> NAnt Nightlys:
>> https://sourceforge.net/projects/nant/files/nant/nightly/
>>
>> NAntContrib Nightlys:
>> https://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/
>>
>> We are still trying to nail down release dates and should be announcing them
>> as soon as they are finalized.
>>
>> The next version number being targeted for NAnt/NAntContrib is currently
>> 0.92. It seems like the natural progression but we are curious if you have 
>> any
>

[nant-dev] Various NAnt Updates

[Ryan Boggs]

Hi all,

Just checking in with some progress that has been occurring in NAnt's
development.  It's not a complete list but there are a few big ones
that I think are worth highlighting.

* The VS project solution files for both NAnt and NAntContrib projects
have been updated to VS2010 format.

* .NET/Mono 1.* runtime support for NAnt has been dropped.  Target
support for .NET/Mono 1.* still exists, however.

* The  task has been updated to use xslCompiledTransform,
which should address the issue described here on Stackoverflow:
http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-closing-tags-with-empty-paired-tags
Thanks to Michael Tutty for the contribution via pull request for this item.

* The  task has been updated to use System.Net.Mail instead of
System.Web.Mail.  During the process of updating this task, additional
features were added that we thought to be very helpful (such as
specifying a reply to address, specifying the port number to send mail
to, indicating whether or not to use an ssl connection, etc).

* More work has gone into the  with the help from Dominik
Guder and Martin Aliger.  From what I understand, there are still a
couple of outstanding issues with this item but the task is working
better with recent versions of msbuild scripts.  This is still a high
priority.

* Quite a bit of work has been put into upgrading the  task
to reference the latest version of NUnit.  I'm happy to say that these
changes are currently in review to be imported into nant/master.  The
version of NUnit being used for this upgrade is 2.6 final (which was
released just a few days ago).  I'm hoping that this will go into
master soon.  I want to say thanks to Charles Poole and the rest of
the NUnit dev team for their help and insight to get the  up
to speed.  They were very helpful in this process.  Anyone interested
in viewing these changes can see them here:
https://github.com/nant/nant/tree/nunitupdates

* The nightly process for both NAnt and NAntContrib projects have
started up again.  This time, an automated process has been setup with
extensive help from Dominik Guder to make sure that new nightly files
are generated whenever changes occur on the master branches of either
project.  The last nightly was built on 2/19/2012 and includes all the
changes listed above except for the nunit changes.  The nightly files
can be found in the following locations:
NAnt Nightlys:
https://sourceforge.net/projects/nant/files/nant/nightly/

NAntContrib Nightlys:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/

We are still trying to nail down release dates and should be
announcing them as soon as they are finalized.

The next version number being targeted for NAnt/NAntContrib is
currently 0.92. It seems like the natural progression but we are
curious if you have any reasons to use a different version number (ie:
should we skip 0.92 and go to 0.95, etc).

That's all I have for now.  I will try to send out these kinds of
notices more often as progress continues.

Thanks,
Ryan

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NUnit work in progress

[Ryan Boggs]

Hi all,

We just want to let everyone know that work is being done to upgrade
the nunit2 task to use the latest version of NUnit.  This work is
being done in the nunitupdates branch at github.com
(https://github.com/nant/nant/tree/nunitupdates).  Feel free to check
it out, fork it, etc but please keep in mind that it is still a work
in progress and it may take a bit of time before it is merged into the
master branch.

Thanks,
Ryan

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Changes to StyleTask

[Ryan Boggs]

Hi,

Just giving everyone a heads up regarding the StyleTask in NAnt.  A
change to this task is being made for it to start using the
XslCompiledTransform class to replace the aging XslTransform class
that has been used all this time.  This change is also an attempt to
remedy an issue that is described here:
http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-closing-tags-with-empty-paired-tags

This change comes from a pull request in github by Michael Tutty.  The
pull request can be found here for those who are interested:
https://github.com/nant/nant/pull/18

Thanks for the contribution Michael. :)

Thanks,
Ryan

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] A few quick things

[Ryan Boggs]

Hi all,

Just some quick bullet points to touch base:

* We are shifting from using the sourceforge bugs/feature
requests/patches section to the issues section of github.com.  So
please start posting new issues there.  If there are old tickets in
the old SF tracker that you feel should be moved, please indicate as
such by changing the group of the ticket to github.com.  We'll
transfer them over as soon as we can.

* The NAnt/NAntContrib projects are now posting commits via twitter.
The twitter account is @nantproject
(https://twitter.com/#!/nantproject).  Whenever there are commits to
the github repos for either project, the summary of those commits will
appear on twitter.

* Runtime support for mono/.net 1.* is no longer being supported for
NAnt/NAntContrib.

* The msbuild/solution files for both projects have been updated to
VS2010 format.

* The wiki pages are slowly being moved over to github's wiki.  Check
out the updated development guide posted there.
https://github.com/nant/nant/wiki/Development-Guide

We'll keep you posted of new developments as they come up.

Thanks,
Ryan

--
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] VS.NET Solution Configurations/Platforms?

[Ryan Boggs]

Hi,

On Nov 14, 2011, at 8:53 AM, Leszek Ciesielski  wrote:

> Does NAnt need the x86 config? Is there actually any P/Invoke code
> that will break with the 'Any CPU' setting? I was under the impression
> that there wasn't.
Not that I can tell.  I haven't seen any p/invoke code anywhere.
> 
> So the 'Debug|Any CPU' and 'Release|Any CPU' platforms should be enough.
Great, thanks for the feedback.

Thanks,
Ryan
> 
> On Mon, Nov 14, 2011 at 5:50 PM, Ryan Boggs  wrote:
>> Hi all,
>> 
>> I'm currently working on upgrading the project/solution files to VS.NET 2010 
>> format.  I was able to convert the existing files successfully but ran into 
>> a snag with the solution configs.  In a nutshell, they are all over the 
>> place. What should be the consensus for the solution configs/platforms?  
>> Debug|x86,  Release|Any CPU?  Any insight is greatly appreciated.

--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] VS.NET Solution Configurations/Platforms?

[Ryan Boggs]

Hi all,

I'm currently working on upgrading the project/solution files to VS.NET 2010 
format.  I was able to convert the existing files successfully but ran into a 
snag with the solution configs.  In a nutshell, they are all over the place. 
What should be the consensus for the solution configs/platforms?  Debug|x86,  
Release|Any CPU?  Any insight is greatly appreciated.

Thanks,
Ryan
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt/NAntContrib has moved to github

[Ryan Boggs]

Hi,

I'm happy to say that we were able to successfully migrate the
sourceforge.net CVS NAnt/NAntContrib repos to github.com.  There are
still some clean-up tasks left to do (ie: update the website links to
point to github.com, update the development guide, etc) but the new
repositories at GitHub are set and ready to go.  The links to the new
repos are listed below.

NAnt:
https://github.com/nant/nant

NAntContrib:
https://github.com/nant/nantcontrib

For those of you who love to code, "fork" either of the projects
through GitHub and start coding/hacking away.  If you don't have a
GitHub account, it's simple to signup.
https://github.com/signup/free

We'll continue to send out updates as soon as new developments come up.

Thanks,
Ryan

--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Move to github.com

[Ryan Boggs]

Hi again,

Just giving everyone an update on our status of the migration.  We are
very close to finishing the move from Sourceforge.net CVS to
github.com.  Last Wednesday, we shut off write access to the old CVS
system to both NAnt and NAntContrib projects to aid in the migration.
As stated previously, the old CVS system will remain online in
readonly mode just for historical purposes.  At this point, the next
email that we will send out for this thread will be officially
announcing the new paths to the github repos.  The estimated completed
date is currently Sunday, November 13.

Thanks,
Ryan

On Tue, Nov 8, 2011 at 9:39 PM, Ryan Boggs  wrote:
> Hi again,
>
> I just wanted to remind everyone that we will be turning off write
> access to both NAnt/NAntContrib cvs repositories at sourceforge.net in
> preparation for the move.  If anyone out there has any last minute
> commits that have been sitting around for awhile, now is the time to
> commit.  Otherwise, you will have to wait until the repositories at
> github have been setup.
>
> Also,
> Another reminder for those who have committed to either projects in
> the past and have a preference of what id/email address to associate
> your past commits with, please visit the online form and provide the
> necessary information so we will use the most current information
> possible.  The form can be found here:
> http://tinyurl.com/3vwsxbm
>
> Thank you to those who have already taken the time to fill out this 
> information.
>
> Thanks,
> Ryan
>
> On Sat, Nov 5, 2011 at 4:53 PM, Ryan Boggs  wrote:
>> Hi,
>>
>> As a result of the feedback received these past few weeks, the
>> decision has been made to move development of the NAnt/NAntContrib
>> projects from sourceforge.net to github.com.  Starting this week, we
>> will begin the process of converting the current sourceforge.net CVS
>> repository so it can be imported into github.com.  The current
>> schedule is as follows:
>>
>> * Wednesday, Nov 9th, 2011 7:00PM PST (GMT - 8 hours) -
>> sourceforge.net CVS repositories will be locked
>> The current cvs repo will be set to readonly on this date.  If you
>> have any changes/updates that need to be committed to cvs, they should
>> be done prior to this date.
>> Please note: The current cvs repo will be kept online after the
>> conversion is complete for historical purposes.  There are no plans to
>> delete this repo at this time.
>>
>> * Thursday, Nov 10th, 2011 7:00PM PST (GMT - 8 hours) - conversion
>> testing from cvs to git
>> We'll begin conversion tests between cvs and git to make sure the
>> information transfers correctly.
>>
>> * Saturday, Nov 12th, 2011 12:00PM PST (GMT - 8 hours) - Setup the git
>> repos with github.com
>> We'll setup the new git repos at github.com.  Once this has been
>> completed, the new repo locations will be announced and the
>> NAnt/NAntContrib websites will be updated to point to the new repo
>> locations.
>>
>> This current timeline is subject to change.  An online calendar has
>> been setup to help keep track of any updates to this schedule[1].
>>
>> For those of you who have directly made commits to either NAnt or
>> NAntContrib cvs repositories, we will be using the sf IDs and email
>> addresses (@users.sourceforge.net) to migrate the
>> committer information to github.com.  If your github.com id differs
>> from your sourceforge.net id, we've setup an online form for you to
>> indicate what should be used when converting your author information.
>> The idea is to make sure that the author information that we migrate
>> is as up-to-date as possible.
>>
>> Please let us know if there are any questions.
>>
>> Thanks,
>> Ryan
>>
>> [1] - Online Calendar - http://tinyurl.com/3hb8cby
>> [2] - Online username form - http://tinyurl.com/3vwsxbm
>>
>

--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Move to github.com

[Ryan Boggs]

Hi,

As a result of the feedback received these past few weeks, the
decision has been made to move development of the NAnt/NAntContrib
projects from sourceforge.net to github.com.  Starting this week, we
will begin the process of converting the current sourceforge.net CVS
repository so it can be imported into github.com.  The current
schedule is as follows:

* Wednesday, Nov 9th, 2011 7:00PM PST (GMT - 8 hours) -
sourceforge.net CVS repositories will be locked
The current cvs repo will be set to readonly on this date.  If you
have any changes/updates that need to be committed to cvs, they should
be done prior to this date.
Please note: The current cvs repo will be kept online after the
conversion is complete for historical purposes.  There are no plans to
delete this repo at this time.

* Thursday, Nov 10th, 2011 7:00PM PST (GMT - 8 hours) - conversion
testing from cvs to git
We'll begin conversion tests between cvs and git to make sure the
information transfers correctly.

* Saturday, Nov 12th, 2011 12:00PM PST (GMT - 8 hours) - Setup the git
repos with github.com
We'll setup the new git repos at github.com.  Once this has been
completed, the new repo locations will be announced and the
NAnt/NAntContrib websites will be updated to point to the new repo
locations.

This current timeline is subject to change.  An online calendar has
been setup to help keep track of any updates to this schedule[1].

For those of you who have directly made commits to either NAnt or
NAntContrib cvs repositories, we will be using the sf IDs and email
addresses (@users.sourceforge.net) to migrate the
committer information to github.com.  If your github.com id differs
from your sourceforge.net id, we've setup an online form for you to
indicate what should be used when converting your author information.
The idea is to make sure that the author information that we migrate
is as up-to-date as possible.

Please let us know if there are any questions.

Thanks,
Ryan

[1] - Online Calendar - http://tinyurl.com/3hb8cby
[2] - Online username form - http://tinyurl.com/3vwsxbm

--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Building nant

[Ryan Boggs]

Hi,

On Tue, Nov 1, 2011 at 8:13 AM, Ramon Smits  wrote:
>
>
> Hi there,
> I am trying to build nant but failing. The readme says :
>     b. Building the Software
>     
>
>     Build NAnt using Microsoft .NET:
>     GNU Make
>     
>         make install MONO= MCS=csc prefix=
> [DESTDIR=]
>         eg. make install MONO= MCS=csc prefix="c:\Program Files"
>     NMake
>     -
>         nmake -f Makefile.nmake install prefix=
> [DESTDIR=]
>
>         eg. nmake -f Makefile.nmake install prefix="c:\Program Files"
>
> I tried the first (gnu make) and it does not really do something. My guess
> is that my make.exe is not gnu make or too old. Running "tools\nmake.exe"
> results in the message : "The image file nmake.exe is valid, but is for a
> machine type other than the current machine.".
> How can I build nant and where to get either gnu make or nmake as this is
> not mentioned in the readme.
Yeah, this is one of the things I want to address pretty soon.  The
copy of nmake that I use should be located in the link provided below:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q132084

It's the link called nmake15.exe.

You could also try installing gmake from here:
http://gnuwin32.sourceforge.net/packages/make.htm

but my experience is that the nmake runs better on Windows but your
milage may very.

> The reason I want to build nant it so upgrade to nunit 2.5.10 as the current
> version cannot handle a lot of nice additions like the TestCase attribute.
This is a high priority for us too.  I've read upon here that some
folks will use the  task to run nunit outside of the nant tasks
just for 2.5.10.  If that'll work for you in the time being, you won't
need to compile nant manually.

Hope this helps.

Thanks,
Ryan
> --
> Ramon
> --
> RSA® Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

--
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Sat, Oct 29, 2011 at 12:07 AM, Dominik Guder  wrote:
> Hi,
>
> I have another request which is high priority for me:
> Review of nant's unit testing concept.
>
> Currently I would like to use test first for implementing and fixing.
> But as far as I can see it is not possible to run nant's test from
> within IDE.
>
> I have a basic unterdstanding why this is done this way (started nearly
> 10 Years ago), but now these tests looks more like integration tests
> than unit tests in TDD thinking.
>
> Maybe we can add another test project where we can run tests within IDE
> and on build server too.
Forgive me but I am having difficulty trying to envision what you are
after here.  I would like to explore it more if you could give an
example on how you see this working.

Thanks,
Ryan
>
> So far Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> Get your Android app more play: Bring it to the BlackBerry PlayBook
> in minutes. BlackBerry App World™ now supports Android™ Apps
> for the BlackBerry® PlayBook™. Discover just how easy and simple
> it is! http://p.sf.net/sfu/android-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Fri, Oct 28, 2011 at 2:17 AM, Stefan Bodewig
 wrote:
> On 2011-10-26, Ryan Boggs wrote:
>
>> On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
>>  wrote:
>
>>> Why do you feel Sourceforge's git offering was insufficient - this is
>>> an honest question as I may be thinking about moving XMLUnit to a
>>> different SCM myself (currently using svn at Sourceforge).
>
>> It just doesn't feel like there is alot of effort on the repo side in
>> terms of code reviews and other tools that sites like github have.
>
> Understood, thanks.
>
>>> When I worked on the log4net release I cursed NAnt's lack of a 
>>> so a big +1 for this.  I also miss .  Badly.
>> I should add  too, eh?
>
> This may be my Ant bias.  log4net's build file is a big mess of
> copy-paste and I think macrodef would help, but maybe there is a
> NAnt-idiomatic way of fixing that without macrodef.  It looks as if
> "call"ing a target is something you'd do more lightly and more often in
> NAnt than in Ant.
Well, either way, it's been added to the list. :)

>
>> It took me awhile to get NAnt to use log4net 1.2.10 because of
>> sharpcvslib's dependency on log4net 1.2.9.  Since I was recently
>> granted commit access to that project, I could see if I could upgrade
>> the dependency in both projects.
>
> Binding redirects?  I don't think we've made API changes that would
> cause trouble otherwise.
>
> Of course, if you can change the dependency then switching to 1.2.11 -
> and to the "new" strong name key - would probably be better.
The problem I had wasn't with the API but the fact that sharpcvslib
seemed hardcoded to 1.2.9.  It gave me some issues during tests using
Mono on *nix.  I can look into this a bit further to see what exactly
is going on.

Thanks,
Ryan
>
> Stefan
>
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Thu, Oct 27, 2011 at 2:47 AM, Dominik Guder  wrote:
> Am 26.10.2011 23:54, schrieb Ryan Boggs:
>> Hey Dominik,
>>
>> On Wed, Oct 26, 2011 at 2:35 PM, Dominik Guder  wrote:
>>> Hi Ryan,
>>>
>>> +1 for github.
>> How many responses should we collect before we make an official
>> decision on this? :)
>
> Just count :) I don't expect many votes for others like bitbucket.
Ok :)
>
>>>
>>> Other proposals:
>>> - Color output. Red for errors, yellow for warning and green for
>>> sucessfull build. I added this to my own net_2.0 build and I'm addicted
>>> to this easily identifying Green successfull build message.
>> Hehehe, That's a good idea.  I actually like that.
>>
>> This would be good for Windows but we should take care in *nix systems
>> as some terminal emulators do not support color.
>
> A short look at mono's BCL implementation showed that Console.ForeGround
>  is basically is implemented. But this must be checked for sure.
> Maybe we can check this with Log4Net team since they are providing the
> ColoredConsoleAppender. (not for Mono currently)
I've seen Mono use Console.Foreground on a *nix machine just fine
using Boo's interactive shell (booish) just fine.  The problem that I
saw was once the user gets out of booish when using certain terminal
types, the output would no longer print to the screen.  All I am
saying is to keep that in mind.  I still like this idea. :)
>
>>>
>>> - fix/polish commandline handling:
>>>    - remove anoying ":" as separator, this prevents you from using tab
>>>      completion in cmd window (even WiX did this with 3.5 release)
>>>    - add double dash as parameter prefix (as used at gnu tools) at least
>>>      for --help and --version
>> One thing I would like to investigate is implementing something like
>> Mono.Options instead of the home grown command args parser.  I've used
>> it in personal projects and it was pretty cool.  That may address your
>> concern here.
>
> This would be fine. But we also check how we can provide backwards
> compatibility.
I think backward compatibility (ie: jkeeping "-t::net-2.0" while
adding something like "-t net-2.0") is definitely possible.  But now
that I am reading the source code, I'm not 100% sure it would work on
.net 2.0.  I'll look into it further...

Thanks,
Ryan
>
> So far Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hey Dominik,

On Wed, Oct 26, 2011 at 2:35 PM, Dominik Guder  wrote:
> Hi Ryan,
>
> +1 for github.
How many responses should we collect before we make an official
decision on this? :)
>
> And we should define/discus a contribution process to ensure that nant
> core will stay as stable as it is currently.
110% agree.  I would like to do this once the repo decision is made.
>
>
> Other proposals:
> - Color output. Red for errors, yellow for warning and green for
> sucessfull build. I added this to my own net_2.0 build and I'm addicted
> to this easily identifying Green successfull build message.
Hehehe, That's a good idea.  I actually like that.

This would be good for Windows but we should take care in *nix systems
as some terminal emulators do not support color.
>
> - solution task/msbuild polishing since there still issues with our
> projects.
Yeah, this is a popular option.  We should probably loop back this
task with the one in NAntContrib to see if we can get this stuff
straightened out.  I'm for this.
>
> SourceControl:
> - move CVS to nantcontrib
> - integrate git
> - polish svn
> - add tfs (see ci-factory)
Yes, yes, yes, and yes.  I also threw Mercurial in that list for good measure.
>
> http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/TF.Tasks/
>
> lower priority:
> - review nant.exe.config: maybe separate net-x and mono-x definitions
>   or one for each target. It is very large and hardly to maintain.
Good one, I agree.  Just not sure of the best approach.  We can
discuss this further.
>
> - fix/polish commandline handling:
>   - remove anoying ":" as separator, this prevents you from using tab
>     completion in cmd window (even WiX did this with 3.5 release)
>   - add double dash as parameter prefix (as used at gnu tools) at least
>     for --help and --version
One thing I would like to investigate is implementing something like
Mono.Options instead of the home grown command args parser.  I've used
it in personal projects and it was pretty cool.  That may address your
concern here.
>
> Check other ci-factory tasks to add them to nantcontrib.
>
> Hint: I found macrodef at ci-factory:
> http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/CIFactory.NAnt.Tasks/Tasks/
Oh wow, pretty cool.

Thanks,
Ryan
>
> It was getting longer and longer.
> So far Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi all,

Thanks for the feedback so far.  It's really great to hear all your
thoughts on these matters.  Please feel free to tell us your thoughts,
if you haven't already.

I went ahead and converted this list to a page on NAnt's wiki for
easier review and maintenance.  I have also made some updates based on
some of the feedback so far.  Please take a look...

https://sourceforge.net/apps/mediawiki/nant/index.php?title=TODO

Thanks,
Ryan

On Wed, Oct 26, 2011 at 8:28 AM, Ryan Boggs  wrote:
> Hi guys,
>
> Now that 0.91 final is out the door, I would like to start discussing
> what items to work on in both NAnt/NAntContrib.  Attached is an html
> file of an outline I put together with thoughts about next steps I
> have had for months (I put it in an attachment just in case your email
> viewers don't handle html emails).  I tried to include items that have
> been discussed in past emails.  All of these items affect both
> NAnt/NAntContrib unless specified otherwise.
>
> One of the things that has been on my mind for months is moving NAnt
> off of cvs.  When I polled that decision some time ago, the general
> consensus was that any move away from cvs would be a step up.  My
> personal feeling is to move from cvs to git or hg to because it is
> more easy for me to work with than cvs.  The first item in my list
> compares the two more popular repo sites out there.  I am partial to
> github.com because I have been using it alot lately for other things
> (working on the Boo language project for example) but I would like to
> hear other thoughts.  I have been experimenting with converting cvs to
> git with a good degree of success (all history, tags, and branches
> come through) but I am sure further tweeking will be necessary.
>
> A side note, when 0.91 final was released, I wasn't sure what the next
> version of NAnt we would be targeting so I just set it to 0.92.  This
> can be discussed further if need be.
>
> Looking forward to hearing your feedback.
>
> Thanks,
> Ryan
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Wed, Oct 26, 2011 at 1:05 PM, Rob Richardson  wrote:
> Ryan,
>
> Towards #net_4, I'd like to see an official download package for each runtime 
> we target.  E.g. one download for .net 1 (the one we have now ... until we 
> kill it off), .net 2, .net 4, mono vX, mono vY, etc -- e.g. a download per 
> #define tag.  Right now the only way to get a #net_4 runtime version is to 
> download source and compile.  That isn't too bad except I have to dig up a VM 
> that still has / I don't mind installing CVS onto.  (Referencing the previous 
> git / github +1.  :D)

Ahhh, I see.  That has been discussed in the past.  I personally do
not have a problem with this setup (others might, IIRC) but we would
probably have to figure out a smart approach to this.  On top of
figuring out whether or not official installers should be built (using
something like msi or NSIS).
>
> With git / github, check 
> out http://sourceforge.net/mailarchive/message.php?msg_id=27967861 and https://github.com/skolima/NAnt.
>   It'd be very, very nice if it was official. rather than cron-cloned.

That would be the plan.  I would like to keep the current cvs around
as a readonly history repo while all of the upcoming changes go into
whatever system is decided upon.  So no cron-cloned, just straight in.

>
> What is still needed with the  task?  I'd like to see more built-in 
> parameters instead of resulting to  but at the end of the day, it gets 
> it done.

Unfortunately, I need to dive in and see.  I am basing my response on
past conversations I have had with other team members.

>
> I'd love to help in any way I can.  I've got a nice library I'd love to share 
> that implements Ant's  and  tasks.  I've also got tasks 
> that list projects given a solution, list project content given a project (to 
> facilitate deploying a website), runs a sql command given a connection string 
> or an app/web.config and (optionally) connection name using SqlClient instead 
> of ODBC, and a few other goodies and tricks.  +1 for  as well, 
> though I didn't write it.  If any of these can get into the official trunk 
> for NAnt or Contrib, all the better.

Those sound like goodies that would be cool to have.
>
> I grant in the near-term you probably need more help in existing tasks than 
> in new ones, and I'm ok with that too.  What're the open issues / tasks?  
> Which would you like me to take on first?

Well, that's the beauty of working on an open source project.  Work on
what you want to work on.  We have items that we wish to work on that
may not reflect what you consider high priorities.  Send in what you
have and we can see where they would fit in.

Like I have said before, we probably need to update our contribution
instructions pretty soon after the repo decision is made.

Thanks,
Ryan
>
> Rob
>
>
>
> - Original Message -
> From: Ryan Boggs 
> To: Rob Richardson 
> Cc: "nant-developers@lists.sourceforge.net" 
> 
> Sent: Wednesday, October 26, 2011 12:35 PM
> Subject: Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks
>
> Hi,
>
> On Wed, Oct 26, 2011 at 12:21 PM, Rob Richardson  wrote:
>> I'll avoid the >athon and just reply at the top.
>>
>> +1 on git and github.  That's more-or-less the lingua franca of 
>> open-source now-a-days.  Being able to accept pull
>> requests would be awesome!  Once it's
>> there, I've got a heap ton of pull requests I'd love to hand off.  To that 
>> end, we should consider a 
>> task in NAnt, and consider moving  to NAntContrib.
> Nice, another plus 1.
> My thinking was to move both NAnt/NAntContrib to a non-CVS repo at the
> same time.  Hopefully, this process will bring the projects closer
> together in scope so we don't have a lag on one side or another.
>>
>> I'd like to see 
>> either get to 2.5.10 or spun off as a separate project.  I had to resort to 
>>  to get 2.5.10
>> working as well.  Many SF patches / posts
>> have upgraded the task throughout the years, but it's never gotten pulled 
>> into the trunk.  If NAnt's cadence is going to be anywhere
>> near previous precedent,  has to move separately to remain relevant.
> My goal is to get it to the latest version, which is 2.5.10 I believe.
> Like I stated in a previous email today, I couldn't get to it during
> 0.91 development because of the amount of effort needed to update NAnt
> to use the new NUnit API.
>>
>> I'd like to also throw in my
>> vote to get  moved from NAntContrib to NAnt.  The  task 
>> hasn't worked for
>> me in 5 years, and thus  has really become an essential part of
>> NAnt.  (Towards the goal

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Wed, Oct 26, 2011 at 12:21 PM, Rob Richardson  wrote:
> I'll avoid the >athon and just reply at the top.
>
> +1 on git and github.  That's more-or-less the lingua franca of 
> open-source now-a-days.  Being able to accept pull
> requests would be awesome!  Once it's
> there, I've got a heap ton of pull requests I'd love to hand off.  To that 
> end, we should consider a 
> task in NAnt, and consider moving  to NAntContrib.
Nice, another plus 1.
My thinking was to move both NAnt/NAntContrib to a non-CVS repo at the
same time.  Hopefully, this process will bring the projects closer
together in scope so we don't have a lag on one side or another.
>
> I'd like to see 
> either get to 2.5.10 or spun off as a separate project.  I had to resort to 
>  to get 2.5.10
> working as well.  Many SF patches / posts
> have upgraded the task throughout the years, but it's never gotten pulled 
> into the trunk.  If NAnt's cadence is going to be anywhere
> near previous precedent,  has to move separately to remain relevant.
My goal is to get it to the latest version, which is 2.5.10 I believe.
 Like I stated in a previous email today, I couldn't get to it during
0.91 development because of the amount of effort needed to update NAnt
to use the new NUnit API.
>
> I'd like to also throw in my
> vote to get  moved from NAntContrib to NAnt.  The  task 
> hasn't worked for
> me in 5 years, and thus  has really become an essential part of
> NAnt.  (Towards the goals of NAnt 2.5, we could shim  to use 
>  for VS 2005+ projects/solutions.)  Tangentially related, if we used 
> the
>  task to build NAnt, we could easily get "Any CPU"
> mode -- a result not currently available in the NAnt release package.
IIRC, the  task needs some more effort before being ported
over.  I know there was work done around VS.NET/msbuild during the
0.91 release cycle but I am not sure how much of that effort related
to the NAntContrib  task.

I was planning on approaching this now anyway.  One of the things I
would like to work on is some kind of sandcastle task for doc building
but it would probably have to rely on that  task.
>
> +1 on moving to .net 2 and
> generics, and a standard #define net_4 release would also be awesome.
I thought we had the net_4.0 preprocessing tag in NAnt already, unless
I am misunderstanding you here.
>
> How can I help?
Love the enthusiasm! :) Speak up and be heard.  I try to read these
messages as much as I can so any input/advice/suggestions you or
anyone else may have, please chime in.  We welcome it. :)

I'm hoping to get a more up-to-date contribution guide going once we
make a decision on the cvs repo situation.  I'll post it once we get
there. :)

Thanks,
Ryan
>
> Rob
>
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

Thanks for your comments, see below.

On Wed, Oct 26, 2011 at 10:57 AM, Leszek Ciesielski  wrote:
> On Wed, Oct 26, 2011 at 6:33 PM, Ryan Boggs  wrote:
>> Hi,
>>
>> On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
>>  wrote:
>>> On 2011-10-26, Ryan Boggs wrote:
>>>
>>>> Now that 0.91 final is out the door, I would like to start discussing
>>>> what items to work on in both NAnt/NAntContrib.  Attached is an html
>>>> file of an outline I put together with thoughts about next steps I
>>>> have had for months (I put it in an attachment just in case your email
>>>> viewers don't handle html emails).
>>>
>>> Jumping in at some random point and as somebody who has a strong Ant
>>> background but doesn't really know NAnt as good as I should.
>>>
>>> I can't say much about your choice of SCM.  Why do you feel
>>> Sourceforge's git offering was insufficient - this is an honest question
>>> as I may be thinking about moving XMLUnit to a different SCM myself
>>> (currently using svn at Sourceforge).
>> It just doesn't feel like there is alot of effort on the repo side in
>> terms of code reviews and other tools that sites like github have.
>> That being said, I've been toying with the idea about using of setting
>> up a git repo on SF to use as a mirror of source.  I am also thinking
>> about keeping the CVS repo at SF live but readonly for historic
>> reasons.
>>
>> One thing I noticed from experience I have with github.com is that it
>> is much easier to share/review code from others than it currently is
>> on SF.
>
> I'm giving a +1 to choosing git and github, in a large part because
> those two are popular and well known. And github's pull management is
> an awesome feature.
:) yup, I concur.
>
>>>
>>> We'll be polling log4net's users about platform support soon.  I also
>>> feel you are safe to require 2.0 at runtime as long as you keep 1.x as
>>> targets.
>> I hope so.
>
> Agree here as well. Although this might (in future) mean quite a large
> rewrite of the NAnt API to make use of the generics.
Eh, it would but I am thinking that the first step of this part is
removing all of the preprocessing statements that separate between
.net 1.0 and .net 2.0. Converting the existing code to use features
from .net/mono 2.0 >= would probably only be worked on if the gains
were significant enough.
>
>>>
>>> When I worked on the log4net release I cursed NAnt's lack of a 
>>> so a big +1 for this.  I also miss .  Badly.
>> I should add  too, eh?
>>>
>>> Have you seen the 1.2.11 release of log4net of about two weeks ago? ;-)
>> I have not.  I'll have to check that out.
>>
>> If activity has restarted for log4net like you say, I should take that
>> item off my list I just sent out.  It was something I have had in mind
>> for months prior when log4net activity seemed non-existent.
>>
>> It took me awhile to get NAnt to use log4net 1.2.10 because of
>> sharpcvslib's dependency on log4net 1.2.9.  Since I was recently
>> granted commit access to that project, I could see if I could upgrade
>> the dependency in both projects.
>
> Updating  task will be tricky, especially if you want to keep
> it working on Mono as well. Any NAnt deployment that I'm aware of has
> resorted to using  instead, because of compatibility problems
> between nunit dlls NAnt bundled and those that the project itself
> used.
Yeah, I am aware of this as I looked into this during 0.91
development.  The NUnit API changed drastically between the current
version NAnt is using today (2.2 I believe) and the latest release
(2.10). Thus, this task was pushed out to avoid further delays of 0.91
final.  From what I gathered from NUnit's docs, 2.5.10 should work on
both mono and .net now so it shouldn't be a problem from that end
(hopefully).
>
> >From the low priority list:
> I'm quite fond of the NAnt website layout :-) And migrating to another
> license requires written permission from every past contributor - this
> would be a hard task to perform. Also, it might not provide any gain
> to end users - development tools don't usually need a permissive
> license, as they are not linked into the end product.
The reasons you just specified are the reasons why they are considered
low priority.  Yeah, the site's current layout still works but it
could use a face lift to bring it to this decade.  Again, low
priority.

As for the license change, it would be a considerable undertaking and
the end payout may not be worth it, 

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi,

On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
 wrote:
> On 2011-10-26, Ryan Boggs wrote:
>
>> Now that 0.91 final is out the door, I would like to start discussing
>> what items to work on in both NAnt/NAntContrib.  Attached is an html
>> file of an outline I put together with thoughts about next steps I
>> have had for months (I put it in an attachment just in case your email
>> viewers don't handle html emails).
>
> Jumping in at some random point and as somebody who has a strong Ant
> background but doesn't really know NAnt as good as I should.
>
> I can't say much about your choice of SCM.  Why do you feel
> Sourceforge's git offering was insufficient - this is an honest question
> as I may be thinking about moving XMLUnit to a different SCM myself
> (currently using svn at Sourceforge).
It just doesn't feel like there is alot of effort on the repo side in
terms of code reviews and other tools that sites like github have.
That being said, I've been toying with the idea about using of setting
up a git repo on SF to use as a mirror of source.  I am also thinking
about keeping the CVS repo at SF live but readonly for historic
reasons.

One thing I noticed from experience I have with github.com is that it
is much easier to share/review code from others than it currently is
on SF.
>
> We'll be polling log4net's users about platform support soon.  I also
> feel you are safe to require 2.0 at runtime as long as you keep 1.x as
> targets.
I hope so.
>
> When I worked on the log4net release I cursed NAnt's lack of a 
> so a big +1 for this.  I also miss .  Badly.
I should add  too, eh?
>
> Have you seen the 1.2.11 release of log4net of about two weeks ago? ;-)
I have not.  I'll have to check that out.

If activity has restarted for log4net like you say, I should take that
item off my list I just sent out.  It was something I have had in mind
for months prior when log4net activity seemed non-existent.

It took me awhile to get NAnt to use log4net 1.2.10 because of
sharpcvslib's dependency on log4net 1.2.9.  Since I was recently
granted commit access to that project, I could see if I could upgrade
the dependency in both projects.

Thanks,
Ryan
>
> Stefan
>
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Next NAnt/NAntContrib TODO Tasks

[Ryan Boggs]

Hi guys,

Now that 0.91 final is out the door, I would like to start discussing
what items to work on in both NAnt/NAntContrib.  Attached is an html
file of an outline I put together with thoughts about next steps I
have had for months (I put it in an attachment just in case your email
viewers don't handle html emails).  I tried to include items that have
been discussed in past emails.  All of these items affect both
NAnt/NAntContrib unless specified otherwise.

One of the things that has been on my mind for months is moving NAnt
off of cvs.  When I polled that decision some time ago, the general
consensus was that any move away from cvs would be a step up.  My
personal feeling is to move from cvs to git or hg to because it is
more easy for me to work with than cvs.  The first item in my list
compares the two more popular repo sites out there.  I am partial to
github.com because I have been using it alot lately for other things
(working on the Boo language project for example) but I would like to
hear other thoughts.  I have been experimenting with converting cvs to
git with a good degree of success (all history, tags, and branches
come through) but I am sure further tweeking will be necessary.

A side note, when 0.91 final was released, I wasn't sure what the next
version of NAnt we would be targeting so I just set it to 0.92.  This
can be discussed further if need be.

Looking forward to hearing your feedback.

Thanks,
Ryan





  High Priority (items that should be addressed first)
  
Options for moving away from CVS

  Sourceforge's repository options seem limited, including types and abilities.  I think it would be best to move the source to a new place better suited for code maintenance, storage, and reviewing.
  
No plans on moving any other services at this time.
  
  Two places that seem most appropriate
  
Moving the repo to github.com

  Primary dvcs is Git
  Used by other projects that use/contributed to NAnt
  
Mono
Boo
Monobjc
  
  Better integrated issue tracking/code review features


  Subversion and mercurial support for the same git repository
  
https://github.com/blog/966-improved-subversion-client-support
http://hg-git.github.com/
  
  Supports an array of features that can be enabled by project


  
Email services
Twitter integration
TeamCity integration
Etc
  

Moving the repo to bitbucket.org

  Available types are Mercurial and Git

  
  

  Owned by atlassian
  Integrated issue tracking features
  Subversion support for mercurial repository
  
Per bitbucket.org docs, feature is available but not supported
  
  Supports an array of features that can be enabled by project


  
Email service
Twitter integration
Etc
  

Recommendation: github.com
  

Drop .Net/Mono 1.* runtime support

  target support will remain

  
  Medium (normal) Priority
  
Move  and  tasks from NAntContrib to NAnt
Rework/enhance subversion tasks in NAntContrib
Add Git and Mecurial source control tasks to NAntContrib
Update  task to use NUnit 2.5.10 (or whatever is latest)

  NUnit 2.5 should now work on both mono & .NET

Look into NMake replacement

  NMake is old and does not seem to be active anymore
  Possible replacement could be a batch or PowerShell script

Look into NDoc replacement

  NDoc has not been maintained in years and has issues with .net 4.0 (workaround for NAnt is currently in place)
  NDoc3, Sandcastle, and monodic could be viable options

Add a sandcastle task to NAntContrib

  Would probably require work on NAntContrib's  task

Add equivalent to Ant's  type
Add simplified syntax to  task to move directories. Like Ant's  task.
Evaluate backend log solutions (unless activity in the log4net project resumes soon)
  
  Low Priority (Nice to haves)
  
Website updates

  It would be nice to revamp the website layout with an updated look and feel

Logo update

  Like the website, the logo could use a face lift as well.

Look into building NAnt plugin for

  Monodevelop
  VS.NET (through Nuget?)

Move to Apache or BSD type license

  This was copied from NAnt's original release plan
  Not sure of feasibility

  



--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a 

[nant-dev] Announcing NAnt/NAntContrib 0.91 Final

[Ryan Boggs]

Sorry for the year long wait

We are proud to announce the final release of NAnt/NAntContrib 0.91.

This release focuses on extending our already strong support for
multiple target frameworks (including .NET 4.0, Mono 4.0, Silverlight,
etc), 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:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.91/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.91/

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

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:
NAnt:
http://sourceforge.net/projects/nant.

NAntContrib:
http://sourceforge.net/projects/nantcontrib.

For more detailed progress on the inner workings of NAnt and
NAntContrib, 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.

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.

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

Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.

Thanks,
Ryan

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Announcing NAnt/NAntContrib 0.91 Release Candidate 1

[Ryan Boggs]

We are proud to announce the first release candidates of NAnt/NAntContrib 0.91.

The primary goal for this release is to continue 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 tightening up both NAnt and NAntContrib
projects for final release.  Unless show stopping bugs are discovered
in the next couple weeks, this code base may represent the 0.91 final
release.

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:
NAnt:
https://sourceforge.net/projects/nant/files/nant/0.91-rc1/

NAntContrib:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/0.91-rc1/

The CVS tag for NAnt 0.91 Release Candidate 1 is:
rel-0-91-rc1

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:
NAnt:
http://sourceforge.net/projects/nant.

NAntContrib:
http://sourceforge.net/projects/nantcontrib.

For more detailed progress on the inner workings of NAnt and
NAntContrib, 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.

About NAntContrib:
NAntContrib is the project for tasks and tools that haven't made it
into the main NAnt distribution yet or for whatever reason don't
belong there.

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

Check the NAntContrib homepage for additional info at
http://nantcontrib.sourceforge.net.

Thanks,
Ryan

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Announcing NAnt 0.91 Beta1

[Ryan Boggs]

Hi,

One thing that I neglected to point out during this announcement was
that right after the release process for NAnt finished, we turned
around and performed the same process for NAntContrib.  So as of
yesterday, version 0.91 Beta1 was released for both NAnt and
NAntContrib.  This should be a continuing process going forward.  Of
course there is more work ahead on this front. :)

Go check it out:
http://nantcontrib.sourceforge.net/

Thanks,
Ryan

-- Forwarded message --
From: Ryan Boggs 
Date: Sun, Sep 25, 2011 at 5:20 PM
Subject: Announcing NAnt 0.91 Beta1
To: nant-developers@lists.sourceforge.net,
nant-us...@lists.sourceforge.net, nant-annou...@lists.sourceforge.net,
mono-list 


We are proud to announce the first beta release of NAnt 0.91.

Many thanks to those who were involved with the development of NAnt
this past year.  Especially to Martin Aliger and Dominik Guder without
whom this release would not have been possible without.

The primary goal for this release is to continue 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.  Some show stopping issues have been resolved 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:
https://sourceforge.net/projects/nant/files/nant/0.91-beta1/

The CVS tag for NAnt 0.91Beta1 is:
rel-0-91-beta1

Instruction for checking out sources from CVS are available here:
https://sourceforge.net/scm/?type=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

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Announcing NAnt 0.91 Beta1

[Ryan Boggs]

We are proud to announce the first beta release of NAnt 0.91.

Many thanks to those who were involved with the development of NAnt
this past year.  Especially to Martin Aliger and Dominik Guder without
whom this release would not have been possible without.

The primary goal for this release is to continue 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.  Some show stopping issues have been resolved 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:
https://sourceforge.net/projects/nant/files/nant/0.91-beta1/

The CVS tag for NAnt 0.91Beta1 is:
rel-0-91-beta1

Instruction for checking out sources from CVS are available here:
https://sourceforge.net/scm/?type=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

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] [NAnt-users] Default excludes for hg and git

[Ryan Boggs]

Hi,

On Tue, Sep 20, 2011 at 5:21 PM, Thierry Lach  wrote:
> The  .*ignore files only have meaning with source control in effect. Since
> the /cvs/, /.svn/, etc dirs are not included, I'd say exclude the  .*ignore
> files and any others related to source control.
Your right, ignore 'em all...

Thanks,
Ryan
>
> On Sep 20, 2011 8:03 PM, "Ryan Boggs"  wrote:
>> Hi,
>>
>> On Tue, Sep 20, 2011 at 2:18 PM, Dominik Guder  wrote:
>>> Hi foks,
>>>
>>> I need your input:
>>>
>>> As you might know nant fileset has a bunch of default excludes.
>>> I want to name mainly cvs and svn administrative folders "**/CVS/**" and
>>> "**/.svn/**" as well as cvs ignore file "**/.cvsignore".
>>>
>>> I want to add some more to this list. Especially for Git and Mercurial.
>>> These are:
>>> "**/.git" and "**/.git/**" for git admin folder
>>> "**/.hg" and "**/.hg/**" for hg admin folder
>> I saw go for it. These should be ignored anyway.
>>>
>>> So what to do with git and hg ignore/config files
>>> There the two ignore files .gitignore and .hgignore should they are
>>> excluded by default too?
>> I would think that these shouldn't be ignored. But it sounds like it
>> is the norm?
>>>
>>> Or the other ones which are starting with .hg* or .git* like
>>> .hgsvnexternals or .hgeol should they be excluded by default too?
>> I am not familiar with these files. I haven't seen them before.
>>>
>>> If there are some other files/folders which should be excluded by
>>> default?
>>>
>>> So far and many thanks in advance.
>>>
>>> Dominik
>>>
>>> --
>>> The answer to the great question of life,
>>> the universe and everything is 42 (Douglas Adams)
>>>
>>>
>>> --
>>> All the data continuously generated in your IT infrastructure contains a
>>> definitive record of customers, application performance, security
>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>> sense of it. Business sense. IT sense. Common sense.
>>> http://p.sf.net/sfu/splunk-d2dcopy1
>>> ___
>>> nant-developers mailing list
>>> nant-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/nant-developers
>>>
>> Thanks,
>> Ryan
>>
>>
>> --
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> ___
>> NAnt-users mailing list
>> nant-us...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nant-users
>

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Default excludes for hg and git

[Ryan Boggs]

Hi,

On Tue, Sep 20, 2011 at 2:18 PM, Dominik Guder  wrote:
> Hi foks,
>
> I need your input:
>
> As you might know nant fileset has a bunch of default excludes.
> I want to name mainly cvs and svn administrative folders "**/CVS/**" and
> "**/.svn/**" as well as cvs ignore file "**/.cvsignore".
>
> I want to add some more to this list. Especially for Git and Mercurial.
> These are:
> "**/.git" and "**/.git/**" for git admin folder
> "**/.hg" and "**/.hg/**" for hg admin folder
I saw go for it.  These should be ignored anyway.
>
> So what to do with git and hg ignore/config files
> There the two ignore files .gitignore and .hgignore should they are
> excluded by default too?
I would think that these shouldn't be ignored.  But it sounds like it
is the norm?
>
> Or the other ones which are starting with .hg* or .git* like
> .hgsvnexternals or .hgeol should they be excluded by default too?
I am not familiar with these files.  I haven't seen them before.
>
> If there are some other files/folders which should be excluded by default?
>
> So far and many thanks in advance.
>
> Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
Thanks,
Ryan

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] SDK docs in nant zipfile

[Ryan Boggs]

Hi Dominik,

On Wed, Sep 14, 2011 at 2:35 PM, Dominik Guder  wrote:
> Hi folks,
>
>
> I started to setup a teamcity build task to automatically create nightlies.
That's wonderful.  I'll take a look at that this weekend.
>
> Everything went ok, but I struggled over ndoc and HtmlHelp generation
> for NAnt-SDK.chm.
> Ndoc's MSDN documentor has a readonly property for hhc.exe. It search in
> %PROGRAMFILES% but this is the wrong location on x64 machines where it
> will be %PROGRAMFILES(x86)%.
>
> Now there are some possible solutions:
> 1) I found a working way to use reflection to set this "internal"
> property on MSDN documentor.
>
> 2) Remove the NAnt-SDK.chm from bin (or nightlies) zip. IMHO
> NAnt-SDK.chm not needed for bin zip. I think a better place could be in
> src zip.
>
> So what do you think? Do someone out there need sdk-doc on a regular basis?
Well, I see a value of having the sdk-doc in the bin file for new
releases as projects that build custom nant tasks are probably not
going want to rebuild nant before building their project.  But this is
a question specific to nightly releases, correct?  If so, I can't
imagine the need for the sdk-doc for nightly releases, especially if
the frequency of nighly releases will be increasing.

Other thoughts?

Thanks,
Ryan
>
> Any other ideas?
>
> So far
> Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the
> BlackBerry® mobile platform with sessions, labs & more.
> See new tools and technologies. Register for BlackBerry® DevCon today!
> http://p.sf.net/sfu/rim-devcon-copy1
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

After all the work that has been put into these VS.NET/MSBuild changes, they
have been finally committed.

Thanks for the hard work guys.

Thanks,
Ryan

On Sun, Aug 7, 2011 at 3:25 PM, Ryan Boggs  wrote:

> Ah, good catches.  I've made the changes in my tree and they are ready for
> committing.
>
> If I don't hear anything else, all of these changes that Dominik, Martin,
> and myself have worked hard on will be committed tonight.
>
> Thanks everyone :)
> Ryan
>
> On Sun, Aug 7, 2011 at 1:33 PM, Dominik Guder  wrote:
>
>> Am 06.08.2011 21:12, schrieb Ryan Boggs:
>>
>>> Hi,
>>>
>>>
>>> I'm thinking that at this point, since I believe I fixed the one or two
>>> things from the comments I received some months ago, I will commit these
>>> changes by end of day Monday unless I hear any objections before then.
>>>  From there, I will perform some nightlys with these changes for public
>>> testing.  Sound good?
>>>
>>>  Another minor fix:
>> please add the missing  entry to xmldoc
>>
>> Thanks
>>
>> Dominik
>>
>> --
>> The answer to the great question of life,
>> the universe and everything is 42 (Douglas Adams)
>>
>>
>> --
>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>> The must-attend event for mobile developers. Connect with experts.
>> Get tools for creating Super Apps. See the latest technologies.
>> Sessions, hands-on labs, demos & much more. Register early & save!
>> http://p.sf.net/sfu/rim-blackberry-1
>> ___
>> nant-developers mailing list
>> nant-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nant-developers
>>
>>
>
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Ah, good catches.  I've made the changes in my tree and they are ready for
committing.

If I don't hear anything else, all of these changes that Dominik, Martin,
and myself have worked hard on will be committed tonight.

Thanks everyone :)
Ryan

On Sun, Aug 7, 2011 at 1:33 PM, Dominik Guder  wrote:

> Am 06.08.2011 21:12, schrieb Ryan Boggs:
>
>> Hi,
>>
>>
>> I'm thinking that at this point, since I believe I fixed the one or two
>> things from the comments I received some months ago, I will commit these
>> changes by end of day Monday unless I hear any objections before then.
>>  From there, I will perform some nightlys with these changes for public
>> testing.  Sound good?
>>
>>  Another minor fix:
> please add the missing  entry to xmldoc
>
> Thanks
>
> Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
>
> --
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> The must-attend event for mobile developers. Connect with experts.
> Get tools for creating Super Apps. See the latest technologies.
> Sessions, hands-on labs, demos & much more. Register early & save!
> http://p.sf.net/sfu/rim-blackberry-1
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

I'm thinking that at this point, since I believe I fixed the one or two
things from the comments I received some months ago, I will commit these
changes by end of day Monday unless I hear any objections before then.  From
there, I will perform some nightlys with these changes for public testing.
Sound good?

Thanks,
Ryan

On Fri, Jul 29, 2011 at 10:28 PM, Ryan Boggs  wrote:

> Anyone had a change to review this yet?  Does it look ok to commit?  Please
> let me know.
>
> Thanks,
> Ryan
>
>
> On Fri, Jul 22, 2011 at 5:17 PM, Ryan Boggs  wrote:
>
>> Updated diff to include changes to the DetermineProductVersion method.
>>
>> I decided that rather than relying on one element or attribute tag,
>> might as well check through them all.  This method will now check for
>> the ProductVersion element first for the msbuild project version.  If
>> that element doesn't exist, it will then check for the
>> TargetFrameworkVersion element.  If neither of those elements exist,
>> it'll then check the ToolsVersion attribute of the Project for a
>> version number.  If none of these items exist in the msbuild file, the
>> method will default to 2.0.  I figured that this approach would be the
>> most detailed in getting the propert msbuild project file's version
>> number.
>>
>> The diff is located in the patches section in sourceforge:
>>
>> https://sourceforge.net/tracker/index.php?func=detail&aid=3311661&group_id=31650&atid=402870
>>
>> I also opened a new review as the old one was getting cluttered.  It is
>> CR-63.
>> https://fisheye1.atlassian.com/cru/CR-63
>>
>> Please let me know if this looks good to commit to the tree.
>>
>> Thanks,
>> Ryan
>>
>> On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs  wrote:
>> > Hi,
>> >
>> > Thought I put in such a patch but it looks like I didn't yet.  I will
>> > see about creating it today.
>> >
>> > Thanks,
>> > Ryan
>> >
>> > On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger 
>> wrote:
>> >> Yes, your solution is better. Depending on ProjectVersion was throwing
>> odd
>> >> exceptions when it was not included (which happens even in VS for
>> whatever
>> >> reason):
>> >>
>> >>
>> >>
>> >>  System.ArgumentException
>> >>  
>> >>  

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Anyone had a change to review this yet?  Does it look ok to commit?  Please
let me know.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 5:17 PM, Ryan Boggs  wrote:

> Updated diff to include changes to the DetermineProductVersion method.
>
> I decided that rather than relying on one element or attribute tag,
> might as well check through them all.  This method will now check for
> the ProductVersion element first for the msbuild project version.  If
> that element doesn't exist, it will then check for the
> TargetFrameworkVersion element.  If neither of those elements exist,
> it'll then check the ToolsVersion attribute of the Project for a
> version number.  If none of these items exist in the msbuild file, the
> method will default to 2.0.  I figured that this approach would be the
> most detailed in getting the propert msbuild project file's version
> number.
>
> The diff is located in the patches section in sourceforge:
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=3311661&group_id=31650&atid=402870
>
> I also opened a new review as the old one was getting cluttered.  It is
> CR-63.
> https://fisheye1.atlassian.com/cru/CR-63
>
> Please let me know if this looks good to commit to the tree.
>
> Thanks,
> Ryan
>
> On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs  wrote:
> > Hi,
> >
> > Thought I put in such a patch but it looks like I didn't yet.  I will
> > see about creating it today.
> >
> > Thanks,
> > Ryan
> >
> > On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger 
> wrote:
> >> Yes, your solution is better. Depending on ProjectVersion was throwing
> odd
> >> exceptions when it was not included (which happens even in VS for
> whatever
> >> reason):
> >>
> >>
> >>
> >>  System.ArgumentException
> >>  
> >>  

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Updated diff to include changes to the DetermineProductVersion method.

I decided that rather than relying on one element or attribute tag,
might as well check through them all.  This method will now check for
the ProductVersion element first for the msbuild project version.  If
that element doesn't exist, it will then check for the
TargetFrameworkVersion element.  If neither of those elements exist,
it'll then check the ToolsVersion attribute of the Project for a
version number.  If none of these items exist in the msbuild file, the
method will default to 2.0.  I figured that this approach would be the
most detailed in getting the propert msbuild project file's version
number.

The diff is located in the patches section in sourceforge:
https://sourceforge.net/tracker/index.php?func=detail&aid=3311661&group_id=31650&atid=402870

I also opened a new review as the old one was getting cluttered.  It is CR-63.
https://fisheye1.atlassian.com/cru/CR-63

Please let me know if this looks good to commit to the tree.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs  wrote:
> Hi,
>
> Thought I put in such a patch but it looks like I didn't yet.  I will
> see about creating it today.
>
> Thanks,
> Ryan
>
> On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger  
> wrote:
>> Yes, your solution is better. Depending on ProjectVersion was throwing odd
>> exceptions when it was not included (which happens even in VS for whatever
>> reason):
>>
>>
>>    
>>      System.ArgumentException
>>      
>>      

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Thought I put in such a patch but it looks like I didn't yet.  I will
see about creating it today.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger  wrote:
> Yes, your solution is better. Depending on ProjectVersion was throwing odd
> exceptions when it was not included (which happens even in VS for whatever
> reason):
>
>
>    
>      System.ArgumentException
>      
>      

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Have you had a chance to review these changes?  Please let me know so
I know what I should do next with this batch of changes.

Thanks,
Ryan

On Thu, Jun 23, 2011 at 10:36 PM, Ryan Boggs  wrote:
> Updated both the diff in NAnt's patches section and atlassian, just in
> case there are issues:
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=3311661&group_id=31650&atid=402870
>
> https://fisheye1.atlassian.com/cru/CR-62
>
> I switched the DetermineProductVersion method to use the
> "ms:PropertyGroup/ms:TargetFrameworkVersion" xml path since it's
> present across all msbuild files.  I also added a check with the c++
> pdb file names.
>
> Thanks,
> Ryan
>
> On Tue, Jun 21, 2011 at 5:36 PM, Ryan Boggs  wrote:
>> Hey Dominik,
>>
>> I saw your notes in the atlassian review and I see your point.  It
>> would probably make more sense to use the "ToolsVersion" property
>> rather than relying on the PropertyGroup/ProductVersion xml node.  I
>> just took a look at some project files created by Sharpdevelop and
>> none of the project files had that xml node but they did have the
>> ToolsVersion property.  I can give this another run through later this
>> week.
>>
>> Thanks,
>> Ryan
>>
>> On Thu, Jun 16, 2011 at 7:26 PM, Ryan Boggs  wrote:
>>> Hi,
>>>
>>> Updated the patch posted in NAnt's SF patches section.  It's the top
>>> one in red.  Also, it looks like there was some feedback on there for
>>> the updates regarding the C++ portion of it.
>>>
>>> Please see inline for other comments.
>>>
>>> On Thu, Jun 16, 2011 at 7:13 AM, Martin Aliger  
>>> wrote:
>>>> I just checked and it correctly resolves all the MSBuild providers on my
>>>> machine.
>>>> Maybe it is becouse I have NAnt.MSBuild.dll in same directory as NAnt.exe?
>>>> Maybe plugins do not resolve when in one of those Framework lib which is
>>>> default for MSBuild assembly atm (no idea why). Or perhaps the order in
>>>> which assemblies are loaded?
>>> It's still not on my machine.  I moved the assembly to the same dir as
>>> the executable. Changed the target framework to net-2.0 and it still
>>> does not pick up the plugins.  I'm kinda wondering if it is my
>>> machine.  Am I the only one experiencing this?
>>>>
>>>> The registration is done in PluginScanner class from Core. All loaded types
>>>> should be send into that (via TypeFactory).
>>> Thanks, I take a look at this as well.
>>>>
>>>> Btw: I noticed, the solution providers from MSBuild assembly got VSNet
>>>> namespace. Maybe it should be changed, for clarity.
>>> I tried switching this too but it didn't make a difference.  Unless
>>> this is really making a difference, I don't see any reason to change
>>> it right now.
>>>>
>>>> Martin Aliger
>>>>
>>>>
>>>>
>>>> -Original Message-
>>>> From: Ryan Boggs [mailto:rmbo...@gmail.com]
>>>> Sent: Thursday, June 16, 2011 3:37 PM
>>>> To: Martin Aliger
>>>> Cc: Dominik Guder; nant-developers@lists.sourceforge.net
>>>> Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild & VSNet Tasks
>>>> Importance: Low
>>>>
>>>> Hi,
>>>>
>>>> Please see inline.
>>>>
>>>> Thanks,
>>>> Ryan
>>>>
>>>> On Jun 16, 2011, at 2:39 AM, "Martin Aliger" 
>>>> wrote:
>>>>
>>>>>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They
>>>>>>> only work with 2002/2003. I would not spend to much time for now in
>>>>>>> sln file handling in VS2005 and up.
>>>>>> Eww, makes sense.  Well, not to let my work go to waste, I think I
>>>>>> know why
>>>>> it isn't working.  The plugins that contains the schema information
>>>>> for
>>>>> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting
>>>>> VS2005+ picked
>>>>> up during NAnt's plugin >discovery phase.
>>>>>> However, I have been having difficulty trying to locate where the
>>>>>> plugin
>>>>> discovery phase occurs in NAnt to make sure that they are getting picked
>>>> up.
>>>>> There is also the fact that the VS2005+ solutio

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Updated both the diff in NAnt's patches section and atlassian, just in
case there are issues:

https://sourceforge.net/tracker/index.php?func=detail&aid=3311661&group_id=31650&atid=402870

https://fisheye1.atlassian.com/cru/CR-62

I switched the DetermineProductVersion method to use the
"ms:PropertyGroup/ms:TargetFrameworkVersion" xml path since it's
present across all msbuild files.  I also added a check with the c++
pdb file names.

Thanks,
Ryan

On Tue, Jun 21, 2011 at 5:36 PM, Ryan Boggs  wrote:
> Hey Dominik,
>
> I saw your notes in the atlassian review and I see your point.  It
> would probably make more sense to use the "ToolsVersion" property
> rather than relying on the PropertyGroup/ProductVersion xml node.  I
> just took a look at some project files created by Sharpdevelop and
> none of the project files had that xml node but they did have the
> ToolsVersion property.  I can give this another run through later this
> week.
>
> Thanks,
> Ryan
>
> On Thu, Jun 16, 2011 at 7:26 PM, Ryan Boggs  wrote:
>> Hi,
>>
>> Updated the patch posted in NAnt's SF patches section.  It's the top
>> one in red.  Also, it looks like there was some feedback on there for
>> the updates regarding the C++ portion of it.
>>
>> Please see inline for other comments.
>>
>> On Thu, Jun 16, 2011 at 7:13 AM, Martin Aliger  
>> wrote:
>>> I just checked and it correctly resolves all the MSBuild providers on my
>>> machine.
>>> Maybe it is becouse I have NAnt.MSBuild.dll in same directory as NAnt.exe?
>>> Maybe plugins do not resolve when in one of those Framework lib which is
>>> default for MSBuild assembly atm (no idea why). Or perhaps the order in
>>> which assemblies are loaded?
>> It's still not on my machine.  I moved the assembly to the same dir as
>> the executable. Changed the target framework to net-2.0 and it still
>> does not pick up the plugins.  I'm kinda wondering if it is my
>> machine.  Am I the only one experiencing this?
>>>
>>> The registration is done in PluginScanner class from Core. All loaded types
>>> should be send into that (via TypeFactory).
>> Thanks, I take a look at this as well.
>>>
>>> Btw: I noticed, the solution providers from MSBuild assembly got VSNet
>>> namespace. Maybe it should be changed, for clarity.
>> I tried switching this too but it didn't make a difference.  Unless
>> this is really making a difference, I don't see any reason to change
>> it right now.
>>>
>>> Martin Aliger
>>>
>>>
>>>
>>> -Original Message-
>>> From: Ryan Boggs [mailto:rmbo...@gmail.com]
>>> Sent: Thursday, June 16, 2011 3:37 PM
>>> To: Martin Aliger
>>> Cc: Dominik Guder; nant-developers@lists.sourceforge.net
>>> Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild & VSNet Tasks
>>> Importance: Low
>>>
>>> Hi,
>>>
>>> Please see inline.
>>>
>>> Thanks,
>>> Ryan
>>>
>>> On Jun 16, 2011, at 2:39 AM, "Martin Aliger" 
>>> wrote:
>>>
>>>>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They
>>>>>> only work with 2002/2003. I would not spend to much time for now in
>>>>>> sln file handling in VS2005 and up.
>>>>> Eww, makes sense.  Well, not to let my work go to waste, I think I
>>>>> know why
>>>> it isn't working.  The plugins that contains the schema information
>>>> for
>>>> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting
>>>> VS2005+ picked
>>>> up during NAnt's plugin >discovery phase.
>>>>> However, I have been having difficulty trying to locate where the
>>>>> plugin
>>>> discovery phase occurs in NAnt to make sure that they are getting picked
>>> up.
>>>> There is also the fact that the VS2005+ solution plugin classes are
>>>> marked as internal but I am not sure >how much of an impact that is making
>>> overall.
>>>>
>>>> Discovery mechanism was made by me and Gert some time ago. I could
>>>> look into it...
>>> Thanks Martin. I thought your names looked familiar. :)
>>>>
>>>> SolutionFactory.cs is main branching thingy. Providers itself are
>>>> registred though Core's IPluginConsumer and ISolutionBuildProvider
>>> interfaces.
>>> I see that and it seems to be working ok with the classes within the
>>> NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
>>> assembly.  If u can point me to where in the code that the solution task
>>> begins to search for plugins in external assemblies, I can research further
>>> as well.
>>>>
>>>> M.
>>>>
>>>
>>>
>>
>

--
All the data continuously generated in your IT infrastructure contains a 
definitive record of customers, application performance, security 
threats, fraudulent activity and more. Splunk takes this data and makes 
sense of it. Business sense. IT sense. Common sense.. 
http://p.sf.net/sfu/splunk-d2d-c1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hey Dominik,

I saw your notes in the atlassian review and I see your point.  It
would probably make more sense to use the "ToolsVersion" property
rather than relying on the PropertyGroup/ProductVersion xml node.  I
just took a look at some project files created by Sharpdevelop and
none of the project files had that xml node but they did have the
ToolsVersion property.  I can give this another run through later this
week.

Thanks,
Ryan

On Thu, Jun 16, 2011 at 7:26 PM, Ryan Boggs  wrote:
> Hi,
>
> Updated the patch posted in NAnt's SF patches section.  It's the top
> one in red.  Also, it looks like there was some feedback on there for
> the updates regarding the C++ portion of it.
>
> Please see inline for other comments.
>
> On Thu, Jun 16, 2011 at 7:13 AM, Martin Aliger  
> wrote:
>> I just checked and it correctly resolves all the MSBuild providers on my
>> machine.
>> Maybe it is becouse I have NAnt.MSBuild.dll in same directory as NAnt.exe?
>> Maybe plugins do not resolve when in one of those Framework lib which is
>> default for MSBuild assembly atm (no idea why). Or perhaps the order in
>> which assemblies are loaded?
> It's still not on my machine.  I moved the assembly to the same dir as
> the executable. Changed the target framework to net-2.0 and it still
> does not pick up the plugins.  I'm kinda wondering if it is my
> machine.  Am I the only one experiencing this?
>>
>> The registration is done in PluginScanner class from Core. All loaded types
>> should be send into that (via TypeFactory).
> Thanks, I take a look at this as well.
>>
>> Btw: I noticed, the solution providers from MSBuild assembly got VSNet
>> namespace. Maybe it should be changed, for clarity.
> I tried switching this too but it didn't make a difference.  Unless
> this is really making a difference, I don't see any reason to change
> it right now.
>>
>> Martin Aliger
>>
>>
>>
>> -Original Message-
>> From: Ryan Boggs [mailto:rmbo...@gmail.com]
>> Sent: Thursday, June 16, 2011 3:37 PM
>> To: Martin Aliger
>> Cc: Dominik Guder; nant-developers@lists.sourceforge.net
>> Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild & VSNet Tasks
>> Importance: Low
>>
>> Hi,
>>
>> Please see inline.
>>
>> Thanks,
>> Ryan
>>
>> On Jun 16, 2011, at 2:39 AM, "Martin Aliger" 
>> wrote:
>>
>>>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They
>>>>> only work with 2002/2003. I would not spend to much time for now in
>>>>> sln file handling in VS2005 and up.
>>>> Eww, makes sense.  Well, not to let my work go to waste, I think I
>>>> know why
>>> it isn't working.  The plugins that contains the schema information
>>> for
>>> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting
>>> VS2005+ picked
>>> up during NAnt's plugin >discovery phase.
>>>> However, I have been having difficulty trying to locate where the
>>>> plugin
>>> discovery phase occurs in NAnt to make sure that they are getting picked
>> up.
>>> There is also the fact that the VS2005+ solution plugin classes are
>>> marked as internal but I am not sure >how much of an impact that is making
>> overall.
>>>
>>> Discovery mechanism was made by me and Gert some time ago. I could
>>> look into it...
>> Thanks Martin. I thought your names looked familiar. :)
>>>
>>> SolutionFactory.cs is main branching thingy. Providers itself are
>>> registred though Core's IPluginConsumer and ISolutionBuildProvider
>> interfaces.
>> I see that and it seems to be working ok with the classes within the
>> NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
>> assembly.  If u can point me to where in the code that the solution task
>> begins to search for plugins in external assemblies, I can research further
>> as well.
>>>
>>> M.
>>>
>>
>>
>

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Updated the patch posted in NAnt's SF patches section.  It's the top
one in red.  Also, it looks like there was some feedback on there for
the updates regarding the C++ portion of it.

Please see inline for other comments.

On Thu, Jun 16, 2011 at 7:13 AM, Martin Aliger  wrote:
> I just checked and it correctly resolves all the MSBuild providers on my
> machine.
> Maybe it is becouse I have NAnt.MSBuild.dll in same directory as NAnt.exe?
> Maybe plugins do not resolve when in one of those Framework lib which is
> default for MSBuild assembly atm (no idea why). Or perhaps the order in
> which assemblies are loaded?
It's still not on my machine.  I moved the assembly to the same dir as
the executable. Changed the target framework to net-2.0 and it still
does not pick up the plugins.  I'm kinda wondering if it is my
machine.  Am I the only one experiencing this?
>
> The registration is done in PluginScanner class from Core. All loaded types
> should be send into that (via TypeFactory).
Thanks, I take a look at this as well.
>
> Btw: I noticed, the solution providers from MSBuild assembly got VSNet
> namespace. Maybe it should be changed, for clarity.
I tried switching this too but it didn't make a difference.  Unless
this is really making a difference, I don't see any reason to change
it right now.
>
> Martin Aliger
>
>
>
> -Original Message-
> From: Ryan Boggs [mailto:rmbo...@gmail.com]
> Sent: Thursday, June 16, 2011 3:37 PM
> To: Martin Aliger
> Cc: Dominik Guder; nant-developers@lists.sourceforge.net
> Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild & VSNet Tasks
> Importance: Low
>
> Hi,
>
> Please see inline.
>
> Thanks,
> Ryan
>
> On Jun 16, 2011, at 2:39 AM, "Martin Aliger" 
> wrote:
>
>>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They
>>>> only work with 2002/2003. I would not spend to much time for now in
>>>> sln file handling in VS2005 and up.
>>> Eww, makes sense.  Well, not to let my work go to waste, I think I
>>> know why
>> it isn't working.  The plugins that contains the schema information
>> for
>> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting
>> VS2005+ picked
>> up during NAnt's plugin >discovery phase.
>>> However, I have been having difficulty trying to locate where the
>>> plugin
>> discovery phase occurs in NAnt to make sure that they are getting picked
> up.
>> There is also the fact that the VS2005+ solution plugin classes are
>> marked as internal but I am not sure >how much of an impact that is making
> overall.
>>
>> Discovery mechanism was made by me and Gert some time ago. I could
>> look into it...
> Thanks Martin. I thought your names looked familiar. :)
>>
>> SolutionFactory.cs is main branching thingy. Providers itself are
>> registred though Core's IPluginConsumer and ISolutionBuildProvider
> interfaces.
> I see that and it seems to be working ok with the classes within the
> NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
> assembly.  If u can point me to where in the code that the solution task
> begins to search for plugins in external assemblies, I can research further
> as well.
>>
>> M.
>>
>
>

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] ***SPAM***BAR*** Re: Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Noted, I will update the patch after work today.  I need to make a couple of 
tweaks to the patch file anyway so this is good timing.

Thanks,
Ryan

On Jun 16, 2011, at 7:31 AM, "Martin Aliger"  wrote:

> Testing this bug, I found another one. Change OutputPath (MSBuildProject
> class) implementation in recent patches to this one:
> 
>internal string OutputPath
>{
>get {
>if (OutputDir != null) return OutputDir.FullName;
>return _msproj.GetEvaluatedProperty("OutputPath");
>}
>}
> 
> Solutions without explicitlly set OutputPath failed. (all mine test cases
> got OutputPath set).
> 
> Martin 
> 
> 
> -Original Message-
> From: Ryan Boggs [mailto:rmbo...@gmail.com] 
> Sent: Thursday, June 16, 2011 3:37 PM
> To: Martin Aliger
> Cc: Dominik Guder; nant-developers@lists.sourceforge.net
> Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild & VSNet Tasks
> Importance: Low
> 
> Hi,
> 
> Please see inline.
> 
> Thanks,
> Ryan
> 
> On Jun 16, 2011, at 2:39 AM, "Martin Aliger" 
> wrote:
> 
>>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They 
>>>> only work with 2002/2003. I would not spend to much time for now in 
>>>> sln file handling in VS2005 and up.
>>> Eww, makes sense.  Well, not to let my work go to waste, I think I 
>>> know why
>> it isn't working.  The plugins that contains the schema information 
>> for
>> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting 
>> VS2005+ picked
>> up during NAnt's plugin >discovery phase.
>>> However, I have been having difficulty trying to locate where the 
>>> plugin
>> discovery phase occurs in NAnt to make sure that they are getting picked
> up.
>> There is also the fact that the VS2005+ solution plugin classes are 
>> marked as internal but I am not sure >how much of an impact that is making
> overall.
>> 
>> Discovery mechanism was made by me and Gert some time ago. I could 
>> look into it...
> Thanks Martin. I thought your names looked familiar. :)
>> 
>> SolutionFactory.cs is main branching thingy. Providers itself are 
>> registred though Core's IPluginConsumer and ISolutionBuildProvider
> interfaces.
> I see that and it seems to be working ok with the classes within the
> NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
> assembly.  If u can point me to where in the code that the solution task
> begins to search for plugins in external assemblies, I can research further
> as well.
>> 
>> M.
>> 
> 

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Please see inline.

Thanks,
Ryan

On Jun 16, 2011, at 2:39 AM, "Martin Aliger"  wrote:

>>> Hi Ryan, sln file handling is some kind of broken since VS2005. They 
>>> only work with 2002/2003. I would not spend to much time for now in 
>>> sln file handling in VS2005 and up.
>> Eww, makes sense.  Well, not to let my work go to waste, I think I know why
> it isn't working.  The plugins that contains the schema information for
> VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting picked
> up during NAnt's plugin >discovery phase.
>> However, I have been having difficulty trying to locate where the plugin
> discovery phase occurs in NAnt to make sure that they are getting picked up.
> There is also the fact that the VS2005+ solution plugin classes are marked
> as internal but I am not sure >how much of an impact that is making overall.
> 
> Discovery mechanism was made by me and Gert some time ago. I could look into
> it...
Thanks Martin. I thought your names looked familiar. :)
> 
> SolutionFactory.cs is main branching thingy. Providers itself are registred
> though Core's IPluginConsumer and ISolutionBuildProvider interfaces.
I see that and it seems to be working ok with the classes within the NAnt.VSNet 
assembly.  It just won't pickup the classes from the NAnt.MSBuild assembly.  If 
u can point me to where in the code that the solution task begins to search for 
plugins in external assemblies, I can research further as well.
> 
> M.
> 

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Thanks for your reply.  Inline comments below.

On Wed, Jun 15, 2011 at 2:05 AM, Dominik Guder  wrote:
> Am 14.06.2011 05:14, schrieb Ryan Boggs:
>> Hi,
>>
>> Just an update.  I'm having issues with trying to process solution
>> files from .NET 2.0 and above with the solution task.  I'm still
>> taking a look at it but it seems that the VS20** plugins in the
>> NAnt.MSBuild assembly are not being picked up by the solution task.
>> I'll keep checking...
>>
>
> Hi Ryan, sln file handling is some kind of broken since VS2005. They
> only work with 2002/2003. I would not spend to much time for now in sln
> file handling in VS2005 and up.
Eww, makes sense.  Well, not to let my work go to waste, I think I
know why it isn't working.  The plugins that contains the schema
information for VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem
to be getting picked up during NAnt's plugin discovery phase.
However, I have been having difficulty trying to locate where the
plugin discovery phase occurs in NAnt to make sure that they are
getting picked up.  There is also the fact that the VS2005+ solution
plugin classes are marked as internal but I am not sure how much of an
impact that is making overall.
>
> The common approach I see is to use solution task with included
> projects, or use msbuild task from nantcontrib (eg. for WiX projects).
I see.  I went straight for the solution files first.  That may have
been my problem.
>
> Basically I think we should provide a basic way to build projects up to
> net-4.0 and add extended features like target version compiling and sln
> file handling when 1.x runtime support was dropped.
Ok, I'm assuming that the statement above fills in the basics, is that correct?
>
> I got my sample compiled against the correct framework recently. I think
> this makes a step further to release 0.91
Are you saying that you are ok with Martin's patch now?  Or did you
have to make some mods?

Thanks,
Ryan
>
> So far
> Dominik
>
>
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Just an update.  I'm having issues with trying to process solution
files from .NET 2.0 and above with the solution task.  I'm still
taking a look at it but it seems that the VS20** plugins in the
NAnt.MSBuild assembly are not being picked up by the solution task.
I'll keep checking...

Thanks,
Ryan

On Tue, Jun 7, 2011 at 5:21 AM, Martin Aliger  wrote:
> Hi,
>
>
>>In addition I had issues to get solution task with included projects and
> without soultionfile property set running. Maybe I did something wrong.
>>(I used only vb projects)
> That should definitelly work. In fact, I would be less suprised if some
> problems arise in sln handling, since we are using/testing bunch of csproj's
> without solution itself.
> Maybe that vbprojs need some tweaks.
>
>>On question: Should it be possible to compile for another targetframework?
> I think this should be handled.
> It should be possible, but I found some problems with it. And since I do not
> use it myself, I didnt test extensivelly. As Ryan wrote, BuildEngine
> wrappers was introduced becouse of it as well as some dynamic loads, dynamic
> listener etc.
> Some testcases for crosscompiling would be great. I think, that hosting
> Framework should be higher that the target, but perhaps opposite could work
> as well. Msbuild4 would need clr4 though.
> But generally, crosscompiling should be possible.
>
> Martin
>
>
>
> --
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hmm,

On Mon, Jun 6, 2011 at 10:28 PM, Dominik Guder  wrote:
> Am 07.06.2011 01:53, schrieb Ryan Boggs:
>> Hi,
>>
>> Martin seems good with the diff I posted.  Has anyone else reviewed it
>> since I posted it last saturday?  The link to the patch is below.
>>
>
> Yes, I did.
>
> One point it is not working with vb solutions, since
> PropertyGroup/ProductVersion exists but is empty in vb projects.
> But this could be fixed easyly.
Is this MSBuild or VSNet tasks?
>
> In addition I had issues to get solution task with included projects and
> without soultionfile property set running. Maybe I did something wrong.
> (I used only vb projects)
I'll check into this.  However, I only test with C# really.
>
> On question: Should it be possible to compile for another
> targetframework? I think this should be handled.
Yes it should.  I believe that is the reason why that new
NAnt.MSBuild.BuildEngine tasks were included.  To handle the cross
compile.

Thanks,
Ryan
>
> So far Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

Martin seems good with the diff I posted.  Has anyone else reviewed it
since I posted it last saturday?  The link to the patch is below.

https://sourceforge.net/tracker/?func=detail&aid=3311661&group_id=31650&atid=402870

Thanks,
Ryan

On Sat, Jun 4, 2011 at 4:23 PM, Ryan Boggs  wrote:
> Hi,
>
> I decided to make a new thread specifically for this update for better
> organization.
>
> The diffs in question have been posted as a single diff in the patches
> tracker in SF.  Direct link is below:
> https://sourceforge.net/tracker/?func=detail&aid=3311661&group_id=31650&atid=402870
>
> I just finished making some slight mods to the original diffs.  I
> restructured it a bit too.  The files that were originally in the
> NAnt/MSBuild/MSBuild directory have been moved to
> NAnt/MSBuild/BuildEngine and the namespace in those files have been
> changed to NAnt.MSBuild.BuildEngine.  Thought this made sense because
> the claases that these files wrap are in a similar namespace.  Just
> tested on .NET 2.0 and everything built and tested out ok when patched
> against cvs.
>
> One thing I wanted to point out.  In the original diff(s) that I
> received from Martin, there was one for Element that made the Location
> property's accessor asymmetric (public get; protected set;).  While I
> like this, it is not currently possible since NAnt still supports .net
> 1.0 runtime.  Since the diff relied on that changed and I didn't know
> why the Location property is not public, I went ahead and created a
> new method in Element called "GetLocation()" that just returns the
> location.  If there is no good reason why the location is not public,
> I would rather go that route.  If there is a valid reason, this is the
> only thing I can think of until .net 1.0 runtime support is dropped
> from NAnt.
>
> Thanks,
> Ryan
>

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Updates to MSBuild & VSNet Tasks

[Ryan Boggs]

Hi,

I decided to make a new thread specifically for this update for better
organization.

The diffs in question have been posted as a single diff in the patches
tracker in SF.  Direct link is below:
https://sourceforge.net/tracker/?func=detail&aid=3311661&group_id=31650&atid=402870

I just finished making some slight mods to the original diffs.  I
restructured it a bit too.  The files that were originally in the
NAnt/MSBuild/MSBuild directory have been moved to
NAnt/MSBuild/BuildEngine and the namespace in those files have been
changed to NAnt.MSBuild.BuildEngine.  Thought this made sense because
the claases that these files wrap are in a similar namespace.  Just
tested on .NET 2.0 and everything built and tested out ok when patched
against cvs.

One thing I wanted to point out.  In the original diff(s) that I
received from Martin, there was one for Element that made the Location
property's accessor asymmetric (public get; protected set;).  While I
like this, it is not currently possible since NAnt still supports .net
1.0 runtime.  Since the diff relied on that changed and I didn't know
why the Location property is not public, I went ahead and created a
new method in Element called "GetLocation()" that just returns the
location.  If there is no good reason why the location is not public,
I would rather go that route.  If there is a valid reason, this is the
only thing I can think of until .net 1.0 runtime support is dropped
from NAnt.

Thanks,
Ryan

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Hi,

On Thu, Jun 2, 2011 at 2:28 PM, Dominik Guder  wrote:
> Am 02.06.2011 18:28, schrieb Ryan Boggs:
>> Hi,
>>
>> Has anyone taken a look at the msbuild/vsnet changes that was posted here 
>> last week?  Please advise.
>>
>> Thanks,
>> Ryan
>>
>
> Hi,
>
> I'm trying to compile this but I have still some issues getting it done
> in net 2.0++
I see it.  There is a namespace conflict it looks like.

Martin,
The files located in the NAnt.MSBuild/MSBuild subdirectory are all
listed in the Microsoft.Build.BuildEngine namespace.  Is this suppose
to be correct?

Thanks,
Ryan
>
> So far Dominik
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Discover what all the cheering's about.
> Get your free trial download today.
> http://p.sf.net/sfu/quest-dev2dev2
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Hi,

On Jun 2, 2011, at 2:28 PM, Dominik Guder  wrote:

> Am 02.06.2011 18:28, schrieb Ryan Boggs:
>> Hi,
>> 
>> Has anyone taken a look at the msbuild/vsnet changes that was posted here 
>> last week?  Please advise.
>> 
>> Thanks,
>> Ryan
>> 
> 
> Hi,
> 
> I'm trying to compile this but I have still some issues getting it done 
> in net 2.0++
Ok, thanks.  I'll take a look at it tonight.

Thanks,
Ryan
> 
> So far Dominik
> -- 
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Discover what all the cheering's about.
> Get your free trial download today. 
> http://p.sf.net/sfu/quest-dev2dev2 
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Hi,

Has anyone taken a look at the msbuild/vsnet changes that was posted here last 
week?  Please advise.

Thanks,
Ryan

On May 27, 2011, at 7:01 AM, Ryan Boggs  wrote:

> Well...
> 
> It sounds like there are still issues with people accessing this
> system so I have attached the diffs for a manual review for the time
> being.  Please reply to this thread if there are any questions with
> the attached diffs.
> 
> Thanks,
> Ryan
> 
> On Wed, May 25, 2011 at 8:29 PM, Ryan Boggs  wrote:
>> Finally uploaded the diffs into the review.  Link is below.  I
>> assigned both you and Gert as reviewers.
>> 
>> https://fisheye1.atlassian.com/cru/CR-62
>> 
>> FYI - It took me a bit to get in earlier today.  Dunno if they had
>> some technical issues or what but I wanted to get you a heads up.
>> 
>> Thanks,
>> Ryan
>> 
>> On Wed, May 25, 2011 at 3:33 PM, Ryan Boggs  wrote:
>>> Ok, I'll do it tonight and post the link once the diffs are posted.  Please 
>>> let me know if you have questions/issues with the system.
>>> 
>>> Thanks,
>>> Ryan
>>> 
>>> On May 25, 2011, at 12:18 PM, Dominik Guder  wrote:
>>> 
>>>> Hi Ryan,
>>>> 
>>>> yes of course go ahead. I might try to put my "CreateInstance" proposal to 
>>>> fisheye too.
>>>> 
>>>> So far Dominik
>>>> 
>>>> Am 25.05.2011 02:52, schrieb Ryan Boggs:
>>>>> Hi,
>>>>> 
>>>>> Any thoughts on this?  I have a handful of diffs from Martin Aliger
>>>>> that I would like you guys to review soon.
>>>>> 
>>>>> Thanks,
>>>>> Ryan
>>>>> 
>>>>> On Sun, May 22, 2011 at 1:38 PM, Ryan Boggs  wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> Since we are a group of more than 2, should we consider going back to
>>>>>> using the atlassian code review that Charles setup awhile ago?  I know
>>>>>> Gert had issues with it in the past but I do still see value to having
>>>>>> something like this.  Thoughts?
>>>>>> 
>>>>>> https://fisheye1.atlassian.com/
>>>> 
>>>> --
>>>> The answer to the great question of life,
>>>> the universe and everything is 42 (Douglas Adams)
>>> 
>> 
> 
> 

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] cvs task change thoughts

[Ryan Boggs]

Hi,

I haven't heard any feedback regarding this since I sent this out over
a week ago so I am assuming that no one has a problem with this.  Just
making sure before I start operating. :)

Thanks,
Ryan

On Sun, May 22, 2011 at 1:19 PM, Ryan Boggs  wrote:
> Hi all,
>
> This is regarding the cvs task in NAnt today.  I want to run this by
> everyone to get everyone's take before anything is done.
>
> I am thinking about altering the cvs task to use the command line
> programs rather than using it's current setup with sharpcvslib for a
> couple of reasons:
>  * sharpcvslib has not been updated/maintained in quite some time.
> (Last official release was over 6 years ago and there hasn't been any
> commit in at least a year if I am reading it right)
>  * The latest sharpcvslib bin seems to be built with log4net 1.2.9.
> This causes problems when trying to update NAnt to use log4net 1.2.10
> on Mono. (This is the main reason why NAnt is still using log4net
> 1.2.9)
>
> This sort of update would require the user to have cvs installed on
> their machine.  This isn't much of an issue for those running Mono on
> a *nix machine but Windows users would need to install it via cygwin
> (unless there is a native Windows program that can be run at the
> command line).
>
> So I am interested in thoughts/feedback from users, especially those
> who use the cvs task.
>
> Thanks,
> Ryan
>

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Finally uploaded the diffs into the review.  Link is below.  I
assigned both you and Gert as reviewers.

https://fisheye1.atlassian.com/cru/CR-62

FYI - It took me a bit to get in earlier today.  Dunno if they had
some technical issues or what but I wanted to get you a heads up.

Thanks,
Ryan

On Wed, May 25, 2011 at 3:33 PM, Ryan Boggs  wrote:
> Ok, I'll do it tonight and post the link once the diffs are posted.  Please 
> let me know if you have questions/issues with the system.
>
> Thanks,
> Ryan
>
> On May 25, 2011, at 12:18 PM, Dominik Guder  wrote:
>
>> Hi Ryan,
>>
>> yes of course go ahead. I might try to put my "CreateInstance" proposal to 
>> fisheye too.
>>
>> So far Dominik
>>
>> Am 25.05.2011 02:52, schrieb Ryan Boggs:
>>> Hi,
>>>
>>> Any thoughts on this?  I have a handful of diffs from Martin Aliger
>>> that I would like you guys to review soon.
>>>
>>> Thanks,
>>> Ryan
>>>
>>> On Sun, May 22, 2011 at 1:38 PM, Ryan Boggs  wrote:
>>>> Hi,
>>>>
>>>> Since we are a group of more than 2, should we consider going back to
>>>> using the atlassian code review that Charles setup awhile ago?  I know
>>>> Gert had issues with it in the past but I do still see value to having
>>>> something like this.  Thoughts?
>>>>
>>>> https://fisheye1.atlassian.com/
>>
>> --
>> The answer to the great question of life,
>> the universe and everything is 42 (Douglas Adams)
>

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Ok, I'll do it tonight and post the link once the diffs are posted.  Please let 
me know if you have questions/issues with the system.

Thanks,
Ryan

On May 25, 2011, at 12:18 PM, Dominik Guder  wrote:

> Hi Ryan,
> 
> yes of course go ahead. I might try to put my "CreateInstance" proposal to 
> fisheye too.
> 
> So far Dominik
> 
> Am 25.05.2011 02:52, schrieb Ryan Boggs:
>> Hi,
>> 
>> Any thoughts on this?  I have a handful of diffs from Martin Aliger
>> that I would like you guys to review soon.
>> 
>> Thanks,
>> Ryan
>> 
>> On Sun, May 22, 2011 at 1:38 PM, Ryan Boggs  wrote:
>>> Hi,
>>> 
>>> Since we are a group of more than 2, should we consider going back to
>>> using the atlassian code review that Charles setup awhile ago?  I know
>>> Gert had issues with it in the past but I do still see value to having
>>> something like this.  Thoughts?
>>> 
>>> https://fisheye1.atlassian.com/
> 
> -- 
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Back to atlassian code review?

[Ryan Boggs]

Hi,

Any thoughts on this?  I have a handful of diffs from Martin Aliger
that I would like you guys to review soon.

Thanks,
Ryan

On Sun, May 22, 2011 at 1:38 PM, Ryan Boggs  wrote:
> Hi,
>
> Since we are a group of more than 2, should we consider going back to
> using the atlassian code review that Charles setup awhile ago?  I know
> Gert had issues with it in the past but I do still see value to having
> something like this.  Thoughts?
>
> https://fisheye1.atlassian.com/
>
> Thanks,
> Ryan
>

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Back to atlassian code review?

[Ryan Boggs]

Hi,

Since we are a group of more than 2, should we consider going back to
using the atlassian code review that Charles setup awhile ago?  I know
Gert had issues with it in the past but I do still see value to having
something like this.  Thoughts?

https://fisheye1.atlassian.com/

Thanks,
Ryan

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] cvs task change thoughts

[Ryan Boggs]

Hi all,

This is regarding the cvs task in NAnt today.  I want to run this by
everyone to get everyone's take before anything is done.

I am thinking about altering the cvs task to use the command line
programs rather than using it's current setup with sharpcvslib for a
couple of reasons:
 * sharpcvslib has not been updated/maintained in quite some time.
(Last official release was over 6 years ago and there hasn't been any
commit in at least a year if I am reading it right)
 * The latest sharpcvslib bin seems to be built with log4net 1.2.9.
This causes problems when trying to update NAnt to use log4net 1.2.10
on Mono. (This is the main reason why NAnt is still using log4net
1.2.9)

This sort of update would require the user to have cvs installed on
their machine.  This isn't much of an issue for those running Mono on
a *nix machine but Windows users would need to install it via cygwin
(unless there is a native Windows program that can be run at the
command line).

So I am interested in thoughts/feedback from users, especially those
who use the cvs task.

Thanks,
Ryan

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] reference assemblies and net-4.0

[Ryan Boggs]

Something else to look at.  A quick google search says that nhibernate
is LGPL.  I'm not sure which version though.

I am not a laywer but I would think that GPL (NAnt's current license)
and LGPL would be compatible.  I would appreciate additional insight
if there are those who are more familiar with license compatibility
than I.

Thanks,
Ryan

On Wed, May 18, 2011 at 11:34 PM, Richard Birkby  wrote:
> NHibernate solved that by building a logging proxy into NHibernate.dll
> and then dynamically binding to log4net.
>
> Are the licenses compatible? You could borrow their implementation.
>
> Richard
>
> On 18 May 2011, at 23:26, Ryan Boggs  wrote:
>
>> The problem isn't NAnt targeting net-4.0-client.  The problem is that
>> one or more of NAnt's dependencies doesn't run well on the client
>> profile.  For example, log4net depends on System.Web which isn't
>> included in the client profile.  It's already been reported in NAnt's
>> bug report while back if I remember right.
>>
>> Thanks,
>> Ryan
>>
>> 2011/5/18 Martin Aliger :
>>> I do not see problem _targeting_ "net-4.0-client" Framework. No real need to
>>> be hosted in that, imho.
>>>
>>> Martin
>>>
>>> -Original Message-
>>> From: Ryan Boggs [mailto:rmbo...@gmail.com]
>>> Sent: Wednesday, May 18, 2011 9:52 PM
>>> To: Martin Aliger
>>> Cc: nant-developers@lists.sourceforge.net
>>> Subject: Re: [nant-dev] reference assemblies and net-4.0
>>>
>>> Hi,
>>>
>>> See inline.
>>>
>>> On Wed, May 18, 2011 at 9:19 AM, Martin Aliger 
>>> wrote:
>>>> I miss some assemblies in this list (latest nightly) for net-4.0.
>>>> Mostly WindowsBase and PresentationFramework. Looks like the list is not
>>> complete.
>>>> Perhaps those should be added with wildcard?
>>> I need to ask about the wildcards in app.config but in the meantime, I went
>>> ahead and committed the two files in question to the app.config file.  I'll
>>> perform another nightly build either tonight or tomorrow for further
>>> testing.
>>>>
>>>>
>>>>
>>>> Also there is something called "NET 4.0 Client Profile". If we want to
>>>> introduce this as separate "Framework" (targettable), there is
>>>> different path for those Reference Assemblies
>>>> ("%ProgramFiles%\Reference
>>>> Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client")
>>> This was brought up in the past.  I think the big issue with this right now
>>> (if I remember right) is that log4net isn't currently setup for the client
>>> profiles.  I recently posted a log4net update I received on this issue to
>>> the nant-dev list but I am not sure if anything was done on their side yet.
>>> In the meantime, anyone have any thoughts on the matter?
>>>>
>>>>
>>>>
>>>>
>>>> >>> basedir="${environment::get-folder-path('ProgramFiles')}/Reference
>>>> Assemblies/Microsoft/Framework/.NETFramework/v4.0">
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>             
>>>>
>>>>             
>>> These two entries were just committed.
>>>>
>>>>             
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Martin
>>>
>>> Thanks,
>>> Ryan
>>>
>>> 
>>> --
>>> What Every C/C++ and Fortran develo

Re: [nant-dev] reference assemblies and net-4.0

[Ryan Boggs]

NLog would be a nice replacement.  Even though 2.0 is still listed as
beta, it claims to support .net 2.0sp1 and up, including client
profiles.  But again, it would have to wait until .net 1.* runtime
support is dropped from NAnt (nlog dropped support for .net 1.*
starting with the 2.0 release).
http://nlog-project.org/nlog2-beta1-release-notes

Thanks,
Ryan

On Wed, May 18, 2011 at 6:15 PM, C. Mundi  wrote:
>
>
> On Wed, May 18, 2011 at 3:31 PM, Dominik Guder  wrote:
>>
>> Am 18.05.2011 22:27, schrieb Martin Aliger:
>> > I do not see problem _targeting_ "net-4.0-client" Framework. No real
>> > need to
>> > be hosted in that, imho.
>> >
>> > Martin
>> >
>>
>> Hi,
>>
>> +1. IMHO we could require full .net 4.0 install for runtime since we
>> need SDK anyways.
>>
>> Besides of this it is easy to build your own log4net and remove web
>> related Appenders. I did this as a proof of concept. And I'm wondering
>> why nobody is going to fix this.
>>
>> So far
>> Dominik
>>
>
> Your wondering is as valid today as it was last year when I noted that
> log4net seems to be a "mature" product abandoned after .NET 2.x.  It turns
> out I was not completely correct.  There has actually been a commit in the
> last year -- 7 months ago.  You have to go back almost two years to find
> another.  I have no choice but to support .NET 4 so I moved on to NLog some
> time ago for my own projects and have been quite happy with it.  It would be
> nice if log4net were more actively maintained.
>
> Good Luck,
> Carlos
>
>
> --
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] reference assemblies and net-4.0

[Ryan Boggs]

Hi,

See inline...

On Wed, May 18, 2011 at 3:31 PM, Dominik Guder  wrote:
> Am 18.05.2011 22:27, schrieb Martin Aliger:
>> I do not see problem _targeting_ "net-4.0-client" Framework. No real need to
>> be hosted in that, imho.
>>
>> Martin
>>
>
> Hi,
>
> +1. IMHO we could require full .net 4.0 install for runtime since we
> need SDK anyways.
I think this could be a short term solution for the time being.  If I
am not mistaken, I believe there was interest in supporting the client
profiles in NAnt (from Gert I believe) so it could be explored.
However, I don't think it will be possible until .net 1.* runtime
support is dropped from NAnt.

On a side note, it doesn't look like Microsoft includes MSBuild in the
client profiles..
http://msdn.microsoft.com/en-us/library/cc656912.aspx
>
> Besides of this it is easy to build your own log4net and remove web
> related Appenders. I did this as a proof of concept. And I'm wondering
> why nobody is going to fix this.
I'm not sure why either.  It doesn't seem like any of the log4net
contributors are doing much with that project anymore.  Gert, please
correct me if I am wrong since I see you listed as one of the "active
committers" on their site.
>
> So far
> Dominik
>
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

Thanks,
Ryan

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Recent commit info

[Ryan Boggs]

Hi,

Just as an FYI, the changes I made a few weeks ago allows NAnt to
build on .NET 4.0 without the need for the Legacy binding.
Unfortunately, it is still needed when targeting < .NET 4.0 when .NET
4.0 is installed on the machine.  This is the reason why I set the
NAnt.Console build file to poke the Legacy binding (set it to false)
when the target is set to 4.0 or later.

I am interested in your approach.  I'm particularly curious of how you
are using the extension methods.

Thanks,
Ryan

On Wed, May 18, 2011 at 3:41 PM, Dominik Guder  wrote:
> Am 18.05.2011 01:48, schrieb Ryan Boggs:
>>
>> Hi,
>>
>> I just performed a commit that should hopefully make building a bit
>> easier with your development with teamcity and other things.  When I
>> was working on the 4.0 compatibility, I was testing the bootstrap on
>> 4.0.  This past commit should allow bootstrapping across the board.
>> Let me know if you have questions.
>>
>> Thanks,
>> Ryan
>>
>
> Hi Ryan,
>
> I dig into this runtime related issue and I found an aproach how we can
> handle this without Legacy Binding. I did this with an extension method. But
> I will do some more tests esp. I need to build my extension assembly in
> nmake bootstrapper.
>
> I will post a follow up the next days.
>
> Dominik
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] reference assemblies and net-4.0

[Ryan Boggs]

The problem isn't NAnt targeting net-4.0-client.  The problem is that
one or more of NAnt's dependencies doesn't run well on the client
profile.  For example, log4net depends on System.Web which isn't
included in the client profile.  It's already been reported in NAnt's
bug report while back if I remember right.

Thanks,
Ryan

2011/5/18 Martin Aliger :
> I do not see problem _targeting_ "net-4.0-client" Framework. No real need to
> be hosted in that, imho.
>
> Martin
>
> -Original Message-
> From: Ryan Boggs [mailto:rmbo...@gmail.com]
> Sent: Wednesday, May 18, 2011 9:52 PM
> To: Martin Aliger
> Cc: nant-developers@lists.sourceforge.net
> Subject: Re: [nant-dev] reference assemblies and net-4.0
>
> Hi,
>
> See inline.
>
> On Wed, May 18, 2011 at 9:19 AM, Martin Aliger 
> wrote:
>> I miss some assemblies in this list (latest nightly) for net-4.0.
>> Mostly WindowsBase and PresentationFramework. Looks like the list is not
> complete.
>> Perhaps those should be added with wildcard?
> I need to ask about the wildcards in app.config but in the meantime, I went
> ahead and committed the two files in question to the app.config file.  I'll
> perform another nightly build either tonight or tomorrow for further
> testing.
>>
>>
>>
>> Also there is something called "NET 4.0 Client Profile". If we want to
>> introduce this as separate "Framework" (targettable), there is
>> different path for those Reference Assemblies
>> ("%ProgramFiles%\Reference
>> Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client")
> This was brought up in the past.  I think the big issue with this right now
> (if I remember right) is that log4net isn't currently setup for the client
> profiles.  I recently posted a log4net update I received on this issue to
> the nant-dev list but I am not sure if anything was done on their side yet.
> In the meantime, anyone have any thoughts on the matter?
>>
>>
>>
>>
>> > basedir="${environment::get-folder-path('ProgramFiles')}/Reference
>> Assemblies/Microsoft/Framework/.NETFramework/v4.0">
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>> 
>>
>> 
> These two entries were just committed.
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>>
>>
>>
>> Martin
>
> Thanks,
> Ryan
>
> 
> --
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] reference assemblies and net-4.0

[Ryan Boggs]

Hi,

See inline.

On Wed, May 18, 2011 at 9:19 AM, Martin Aliger  wrote:
> I miss some assemblies in this list (latest nightly) for net-4.0. Mostly
> WindowsBase and PresentationFramework. Looks like the list is not complete.
> Perhaps those should be added with wildcard?
I need to ask about the wildcards in app.config but in the meantime, I
went ahead and committed the two files in question to the app.config
file.  I'll perform another nightly build either tonight or tomorrow
for further testing.
>
>
>
> Also there is something called „NET 4.0 Client Profile“. If we want to
> introduce this as separate „Framework“ (targettable), there is different
> path for those Reference Assemblies ("%ProgramFiles%\Reference
> Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client")
This was brought up in the past.  I think the big issue with this
right now (if I remember right) is that log4net isn't currently setup
for the client profiles.  I recently posted a log4net update I
received on this issue to the nant-dev list but I am not sure if
anything was done on their side yet.  In the meantime, anyone have any
thoughts on the matter?
>
>
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
> 
>
> 
These two entries were just committed.
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
> Martin

Thanks,
Ryan

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Recent commit info

[Ryan Boggs]

Hi,

I just performed a commit that should hopefully make building a bit
easier with your development with teamcity and other things.  When I
was working on the 4.0 compatibility, I was testing the bootstrap on
4.0.  This past commit should allow bootstrapping across the board.
Let me know if you have questions.

Thanks,
Ryan

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Fwd: [jira] [Commented] (LOG4NET-174) log4net.dll references assemblies that are not part of the .NET 3.5 SP1 client profile

[Ryan Boggs]

FYI,

Just wanted to share this email I rec'd this morning.  This issue in question 
deals with .net 3.5 client profile builds on log4net which I briefly tried 
looking at last fall.  Looks like another solution has been suggested.  Dunno 
if it will go anywhere though.  Here's to hoping.. :)

Thanks,
Ryan

Begin forwarded message:

> From: "Jon S Akhtar (JIRA)" 
> Date: May 16, 2011 7:35:48 AM PDT
> To: rmbo...@gmail.com
> Subject: [jira] [Commented] (LOG4NET-174) log4net.dll references assemblies 
> that are not part of the .NET 3.5 SP1 client profile
> 

> 
>[ 
> https://issues.apache.org/jira/browse/LOG4NET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034031#comment-13034031
>  ] 
> 
> Jon S Akhtar commented on LOG4NET-174:
> --
> 
> I just added a CLIENT define, and placed it in the correct 7 locations 
> usually "!NETCF && !SSCLI && !CLIENT".
> 
> This builds a client profile version of the assembly. I think that it follows 
> the methodology used to handle the other platform cases, so I don't really 
> see it being a major problem design-wise.
> 
> 
>> log4net.dll references assemblies that are not part of the .NET 3.5 SP1 
>> client profile
>> --
>> 
>>Key: LOG4NET-174
>>URL: https://issues.apache.org/jira/browse/LOG4NET-174
>>Project: Log4net
>> Issue Type: Bug
>> Components: Builds
>>   Affects Versions: 1.2.10
>>Environment: .Net 3.5 SP1
>>   Reporter: Kuno Meyer
>> 
>> .Net 3.5 SP1 / VS 2008 SP1 has a new build feature: the "client-only 
>> framework subset" switch in the projects settings, meaning that the 
>> developer can specify that only a limited subset of the .Net framework is 
>> used. This helps in reducing the size of installers that include the .Net 
>> framework.
>> Unfortunately, log4net.dll (1.2.10) has references to System.Web, which is 
>> not part of this "client-only framework subset". This leads to the following 
>> compilation warning:
>> <<<
>> C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning 
>> MSB3253: The referenced assembly "log4net, Version=1.2.10.0, 
>> Culture=neutral, PublicKeyToken=1b44e1d426115821, 
>> processorArchitecture=MSIL" has a dependency on "System.Web, 
>> Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is 
>> not listed as part of the "Client" TargetFrameworkSubset. If this dependent 
>> reference is required, you may get compilation errors.
> 
>> My proposal is to split log4net.dll into a new log4net.dll (core+generic 
>> appenders) and into a separate appender DLL (log4net.server.dll) for 
>> deployment on servers only.
> 
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates

[Ryan Boggs]

Where did u post your changes originally?

Thanks,
Ryan

On May 11, 2011, at 12:46 AM, "Martin Aliger"  wrote:

> I got same need and implemented that. But it never made its way to trunk
> (posted atleast twice).
> 
> I'll repost all mine changes today or tommorow. There are known problems
> (wpf, silverlight), but most of 4.0 solution stuff works well.
> 
> Martin Aliger
> 
> -Original Message-
> From: Dominik Guder [mailto:o...@guder.org] 
> 
> - I also need the possibility to add msbuild properties to solution task to
> define a snk file on solution task and not in assebmlyinfo.cs
> 
> 
> 
> --
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates

[Ryan Boggs]

Looking forward to hearing your ideas. :)

Thanks,
Ryan

On Thu, May 5, 2011 at 6:04 PM, Dominik Guder  wrote:
> Am 04.05.2011 07:19, schrieb Ryan Boggs:
>> Hi,
>>
>> Just checking in real quick.  I just merged the branch I was working
>> on into HEAD this evening.  If everything goes well, I should start
>> kicking out more nightly releases by this weekend, if not before.
>>> From there, I'll need to decide the future release schedule.  Once it
>> is decided, it will be posted here.
>>
>> Anyone have any thoughts or want to pitch in? :)
>>
>> Thanks,
>> Ryan
>>
>
> So basically I'm willing to help. I have some ideas and some special
> needs. I also have a patch for nantcontrib vb6 task ready.
>
> Maybe I find some the next day to look at latest roadmap.
>
> So far Dominik
>
>
> --
> The answer to the great question of life,
> the universe and everything is 42 (Douglas Adams)
>
> --
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Updates

[Ryan Boggs]

Hi,

Just checking in real quick.  I just merged the branch I was working
on into HEAD this evening.  If everything goes well, I should start
kicking out more nightly releases by this weekend, if not before.
>From there, I'll need to decide the future release schedule.  Once it
is decided, it will be posted here.

Anyone have any thoughts or want to pitch in? :)

Thanks,
Ryan

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Is NAnt 0.85 Supports for Visual Studio 2010 or .NET Framework 4.0?

[Ryan Boggs]

Not officially, no.  

If you want 4.0 support, you need NAnt 0.91 alpha2.  The only major issue with 
this release is a security exception that has only occurred with a select 
number of people so far that I'm trying to address.  The current workaround for 
this is to build NAnt 0.91 alpha2 from source.

Hope this helps,
Ryan

On Apr 1, 2011, at 6:31 AM, Vinod Soni  wrote:

> 
> Dear Friends, 
> 
> I am going for the visual studio 2010 enhancements in build script, So i want 
> to confirm Is NAnt 0.85 Supports for Visual Studio 2010 or .NET Framework 
> 4.0? 
> I am using Nant 0.85. 
> 
> Thanks & Regards
> Vinod Soni - MCTS
> Enterprise Architecture (Humana)
> Desk: +91-120-4398818
> Mobile:+91-989969
> 
> Anything is possible.  All it takes is a little research. (Me)
> 
> The information transmitted is intended only for the person or entity to 
> which it is addressed and may contain CONFIDENTIAL material. If you receive 
> this material/information in error, please contact the sender and delete or 
> destroy the material/information.
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself; 
> WebMatrix provides all the features you need to develop and 
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] NAnt on IRC

[Ryan Boggs]

Hey Guys,

I just wanted to put a reminder out there that there is an IRC channel
for NAnt over on irc.freenode.net.  The room name is #nant.  I have
been trying to make it a habit of showing up here in an effort to keep
things going.

Thanks,
Ryan

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Q: version of log4net in nant

[Ryan Boggs]

Hi again,

On Mon, Nov 8, 2010 at 9:19 AM, C. Mundi  wrote:
>
> Hi.
>
> I apologize if I missed something, but I did not find this definitively
> addressed in the nant-dev archives.  Pointers to clues will be graciously
> accepted.
>
> This post is motivated by my interest in getting NAnt to work on .NET 4,
> with all its changes to the Code Access Security model.  I am one of the
> people for whom installation of .NET 4 breaks the NAnt runtime (for all
> target frameworks).  On to the question!
>
> Question: Is there a technical reason for the nightly nant to use version
> 1.2.9 of log4net instead of the latest 1.2.10 ?  (I infer this from the DLL
> header.)
>
> I realize that the widely-assumed guarantee of .NET backward compatibility
> should make this irrelevant, an assumption stated at
> http://logging.apache.org/log4net/release/framework-support.html.   But it
> also seems noteworthy that log4net has not yet released a .NET 4 build *and*
> nightly NAnt appears to die for me with a System.Security.SecurityException
> originating in log4net.  I hypothesize that the log4net project has not yet
> dealt with the breaking CAS changes in .NET 4.  If this hypothesis is
> correct, then updating log4net to .NET 4 could improve the compatibility of
> NAnt with .NET 4.
>
> So... before I consider making log4net play nice with .NET 4, I'd like to
> know if there is any reason not to start with log4net 1.2.10.
Decent question.  If you are going to test on a Windows platform using
.NET, go ahead and give log4net 1.2.10 a shot.  We haven't moved from
1.2.9 because there is some issues with 1.2.10 working on *nix/mono
platforms due to sharpcvslib's specific dependency on log4net 1.2.9.
I found this out the hard way when trying to do the upgrade last week.
 Switching to 1.2.10 on a windows platform using .NET seemed to work
out ok.

Thanks,
Ryan
>
> Thanks,
> Carlos
>
> --
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Blog Post - Various Updates

[Ryan Boggs]

https://sourceforge.net/apps/wordpress/nant/2010/10/23/various-updates/

Thanks,
Ryan

--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Thoughts on moving NAnt to git

[Ryan Boggs]

Hey Guys,

How do you all feel about moving NAnt to git?  Do you guys think that
it would be a welcome change?

Thanks,
Ryan

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Announcing NAnt 0.91 Alpha2

[Ryan Boggs]

Announcing NAnt 0.91 Alpha2
We are proud to announce the second alpha release of NAnt 0.91.

The primary goal for this release is to continue 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.  Some show stopping issues have been resolved 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-alpha2

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.

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] nant and nantcontrib source control

[Ryan Boggs]

Hey,

Yeah, that is the plan eventually.  However, there currently is no ETA
at the moment.  When we do decide to make the transition, it'll most
likely be in stages and we'll announce it once we start the process.

Thanks,
Ryan

On Sun, Jul 4, 2010 at 12:05 PM, Nick Durcholz  wrote:
> I noticed the git repo link on sourceforge for nant, which is empty at the
> momentdoes this mean you guys are going to move away from CVS?  (that
> would be just swell imo)
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] [Mono-list] Off Topic: NAnt on Linux error CS0234

[Ryan Boggs]

Hi,

I don't remember seeing this in any of the NAnt mailing lists.  Maybe
it didn't go through...

Anyway,
Looking at your NAnt.build file. I believe that you need the full file
name of the assembly that you are wanting to reference.


Ex:
   









   

Look at the example at the bottom of:
http://nant.sourceforge.net/release/latest/help/tasks/csc.html

Hope this helps.

Thanks,
Ryan

On Wed, Jun 9, 2010 at 11:41 PM,   wrote:
>
> Hi all,
>
> I posted this on the NAnt maling list a week ago. But sadly I got no
> response...
>
> Maybe this problem is known by a user on this list:
>
>
> 
>
> Hi all,
>
> I'm using the NAnt 0.9 release on Linux 11.2/Gnome.
> Monodevelop 2.4 (Beta)
> Mono 2.6.3
>
> This error is not new to the list: My problem is, that the code compiles
> with Monodevelop but not with NAnt. It stops with error CS0234. See build
> output below. Funny is that the error detail belongs to standard mono
> libraries/DLLs. This might be a configuration problem, but I cannot figure
> out what it is...
>
> Maybe one could give me a clue...
>
> Regards
>
> Niklas
>
>
> Build output (snippet):
>
> [csc]
> /home/dev/Silva/Source/Ways/Core/Application/ServiceRequest/Client/Soap/Serv
> iceRequestSoapProxy.cs(55,67): error CS0234: The type or namespace name
> `Services' does not exist in the namespace `System.Web'. Are you missing an
> assembly reference?
> [csc]
> /home/dev/Silva/Source/Ways/Core/DataAccess/Provider/Ado/AdoDataAccessProvid
> erConfiguration.cs(2,14): error CS0234: The type or namespace name `Data'
> does not exist in the namespace `System'. Are you missing an assembly
> reference?
> [csc] Compilation failed: 2 error(s), 275 warnings
>
>
> Assembly data (from Monodevelop):
>
> // Assembly System.Data, Version 2.0.0.0 [AssemblyTitle ("System.Data.dll")]
> [AssemblyDescription ("System.Data.dll")] [AssemblyDefaultAlias
> ("System.Data.dll")] [AssemblyCompany ("MONO development team")]
> [AssemblyProduct ("MONO Common language infrastructure")] [AssemblyCopyright
> ("(c) various MONO Authors")] [SatelliteContractVersion ("2.0.0.0")]
> [AssemblyInformationalVersion ("2.0.50727.1433")] [CLSCompliant (true)]
> [NeutralResourcesLanguage ("en-US")] [ComVisible (false)]
> [AllowPartiallyTrustedCallers ()] [AssemblyDelaySign (true)]
> [AssemblyKeyFile ("../ecma.pub")] [AssemblyFileVersion ("2.0.50727.1433")]
> [ComCompatibleVersion (1, 0, 3300, 0)] [InternalsVisibleTo ("System.Design,
> PublicKey=002404809400060200245253413100040100010007
> d1fa57c4aed9f0a32e84aa0faefd0de9e8fd6aec8f87fb03766c834c99921eb23be79ad9d5dc
> c1dd9ad236132102900b723cf980957fc4e177108fc607774f29e8320e92ea05ece4e821c0a5
> efe8f1645c4c0c93c1ab99285d622caa652c1dfad63d745d6f2de5f17e5eaf0fc4963d261c8a
> 12436518206dc093344d5ad293")]
> [InternalsVisibleTo ("System.Web,
> PublicKey=002404809400060200245253413100040100010007
> d1fa57c4aed9f0a32e84aa0faefd0de9e8fd6aec8f87fb03766c834c99921eb23be79ad9d5dc
> c1dd9ad236132102900b723cf980957fc4e177108fc607774f29e8320e92ea05ece4e821c0a5
> efe8f1645c4c0c93c1ab99285d622caa652c1dfad63d745d6f2de5f17e5eaf0fc4963d261c8a
> 12436518206dc093344d5ad293")]
> [RuntimeCompatibility ()]
>
>
> // Assembly System.Web.Services, Version 2.0.0.0 [AssemblyTitle
> ("System.Web.Services.dll")] [AssemblyDescription
> ("System.Web.Services.dll")] [AssemblyDefaultAlias
> ("System.Web.Services.dll")] [AssemblyCompany ("MONO development team")]
> [AssemblyProduct ("MONO Common language infrastructure")] [AssemblyCopyright
> ("(c) various MONO Authors")] [SatelliteContractVersion ("2.0.0.0")]
> [AssemblyInformationalVersion ("2.0.50727.1433")] [NeutralResourcesLanguage
> ("en-US")] [ComVisible (false)] [AllowPartiallyTrustedCallers ()]
> [CLSCompliant (true)] [AssemblyDelaySign (true)] [AssemblyKeyFile
> ("../msfinal.pub")] [AssemblyFileVersion ("2.0.50727.1433")]
> [CompilationRelaxations (8)] [Debuggable (2)] [RuntimeCompatibility ()]
>
>
>
> GAC info:
>
> d...@linux-gh99:~/Silva/Release/Build> locate System.Web.Services.dll
> /home/dev/.config/MonoDevelop/CodeCompletionData/_usr_lib_mono_2.0_System.Web.Services.dll.pidb
> /usr/lib/mono/1.0/System.Web.Services.dll
> /usr/lib/mono/2.0/System.Web.Services.dll
> /usr/lib/mono/gac/System.Web.Services/1.0.5000.0__b03f5f7f11d50a3a/System.Web.Services.dll
> /usr/lib/mono/gac/System.Web.Services/1.0.5000.0__b03f5f7f11d50a3a/System.Web.Services.dll.mdb
> /usr/lib/mono/gac/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
> /usr/lib/mono/gac/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll.mdb
>
> d...@linux-gh99:~/Silva/Release/Build> locate System.Data.dll
> /home/dev/.config/MonoDevelop/CodeCompletionData/_usr_lib_mono_2.0_System.Data.dll.pidb
> /usr/lib/mono/1.0/System.Data.dll
> /usr/lib/mono/2.0/System.Data.dll
> /usr/lib/mono/gac/System.Data/1.0.5000.0__b77a5c561934e089/System.Data

[nant-dev] Announcing NAnt 0.91 Alpha1

[Ryan Boggs]

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-dev] NAnt Updates/A call to arms

[Ryan Boggs]

Hi all,

If you haven't reviewed the NAnt blog lately, I wrote an entry to
request for volunteer for both NAnt and NAntContrib (especially).  The
blog post is here:
https://sourceforge.net/apps/wordpress/nant/2010/05/24/a-call-to-arms/

As you can see, we are in need of help. As it stands right now, there
are about 3/4 active people just for the NAnt project. Our main focus
has been revitalizing the NAnt core project and so far we have been
successful.  With that being said, a lot of people use NAntContrib
together with NAnt, so it's critical to bring that up that project
up-to-date as well.

The ideal candidates is anyone who is passionate about NAnt or
NAntContrib, and preferably an active user who can inject some life
into the project. If you have the time and experience, please take a
look at some of the open tickets in either project that interests you
and start coding away. There is also some great information within the
wiki, found here:
https://sourceforge.net/apps/mediawiki/nant/index.php?title=Development_Guide#Contributing_code
on how to get started and to contribute code. If you have the time and
interest, and is looking to be more involved, we are also looking for
a leader to help jump start NAntContrib as well!

Oh, one other thing to keep in mind.  When submitting a bug report,
please submit it to the appropriate project.  If it deals with
something within the NAntContrib, please open a ticket in the
NAntContrib area.  Since these projects will not combined anytime
soon, it is good to keep the bug reports filed appropriately.

Thanks,
The NAnt Core Team

--

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

[nant-dev] .NET 4.0 Support in the latest Nightly Release

[Ryan Boggs]

Hi Guys,

Just letting everyone know that the nightly release that went out
today has .NET 4.0 support that REALLY needs testing.  Please test to
your heart's content and report any bugs that you guys come across.

You can go to the file section in sourceforge and download the files
under nightly/2010-05-12.
https://sourceforge.net/projects/nant/files/

Thanks,
Ryan

--

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

[nant-dev] Announcing NAnt 0.90

[Ryan Boggs]

We are proud to announce the final release of NAnt 0.90, the first
final release of NAnt in a VERY long time.

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.90 is:
rel-0-90

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.

--

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

[nant-dev] Announcing NAnt 0.90 Release Candidate 1

[Ryan Boggs]

Announcing NAnt 0.90-rc1

The first release candidate 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

Unless there are any real show stoppers reported, we will be moving
the final release up one week from May 15th to May 9th.  From there we
will begin focusing our attention to 0.91.

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 Release Candidate 1 is:
rel-0-90-rc1

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.

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

[nant-dev] NAnt 0.90 small progress update

[Ryan Boggs]

Hi all,

Just wanted to let everyone know, we are still working hard behind the
scenes on NAnt 0.90 and expect the first Release Candidate (RC)
release this weekend.  In the meantime, check out the NAnt blog when
you get a minute.  You might find something interesting there. :)

https://sourceforge.net/apps/wordpress/nant/

Thanks,
Ryan

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