Menu
▾
▴
nantcontrib-developer — General Developers List
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(20) |
Jul
(14) |
Aug
(42) |
Sep
(7) |
Oct
(20) |
Nov
(6) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(14) |
Feb
(37) |
Mar
(12) |
Apr
(45) |
May
(20) |
Jun
(55) |
Jul
(26) |
Aug
(2) |
Sep
(41) |
Oct
(29) |
Nov
(56) |
Dec
(43) |
| 2004 |
Jan
(62) |
Feb
(26) |
Mar
(55) |
Apr
(73) |
May
(47) |
Jun
(16) |
Jul
(47) |
Aug
(60) |
Sep
(87) |
Oct
(99) |
Nov
(73) |
Dec
(85) |
| 2005 |
Jan
(53) |
Feb
(34) |
Mar
(36) |
Apr
(58) |
May
(38) |
Jun
(26) |
Jul
(31) |
Aug
(22) |
Sep
(9) |
Oct
(17) |
Nov
(9) |
Dec
(3) |
| 2006 |
Jan
(12) |
Feb
(4) |
Mar
(10) |
Apr
(6) |
May
|
Jun
(7) |
Jul
(16) |
Aug
(2) |
Sep
(14) |
Oct
(6) |
Nov
(5) |
Dec
|
| 2007 |
Jan
(2) |
Feb
(11) |
Mar
(5) |
Apr
(4) |
May
|
Jun
(9) |
Jul
(12) |
Aug
(3) |
Sep
|
Oct
(2) |
Nov
(6) |
Dec
(1) |
| 2008 |
Jan
(7) |
Feb
(8) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
(7) |
Sep
(3) |
Oct
(6) |
Nov
|
Dec
(1) |
| 2009 |
Jan
|
Feb
|
Mar
(3) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
(4) |
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Derek F. <dez...@gm...> - 2015-09-29 11:13:31
|
Hi all, I've submitted an issue to the github issue tracker, here: https://github.com/nant/nantcontrib/issues/40 We're using NAntContrib for some IIS website install operations and recently came across this issue with websites which old have secure binding specified. I'm planning on fixing this issue and sending a pull request however I can't see any tests for the web tasks in the source so I'm concerned there's a risk my change will introduce a regression without me knowing. Before I go ahead I wanted to check whether there's a separate testing project somewhere or whether I'm missing something else? Thanks, Derek -- Derek Fowler |
|
From: Jigisha <jig...@ya...> - 2015-05-01 17:07:16
|
Hi, Is there any way to log build error message to different log file in case of failure and skip entire build log details? Thanks, Jigisha. |
|
From: Ryan B. <rm...@gm...> - 2012-06-09 17:10:03
|
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 nan...@li.... 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 |
|
From: Ryan B. <rm...@gm...> - 2012-05-28 00:08:51
|
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 |
|
From: Ryan B. <rm...@gm...> - 2012-05-24 04:07:10
|
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 nan...@li.... 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 |
|
From: Ryan B. <rm...@gm...> - 2012-05-21 05:50:42
|
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 |
|
From: SourceForge.net <no...@so...> - 2012-05-16 22:21:32
|
Bugs item #3527410, was opened at 2012-05-16 15:21 Message generated for change (Tracker Item Submitted) made by rubicon_hfr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3527410&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Other Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: hfrmobile (rubicon_hfr) Assigned to: Nobody/Anonymous (nobody) Summary: WHY GitHub? Initial Comment: WHY I am forced to create my 1000th account? WHY does GitHub not support OpenID. WHY???? Just liked to report an issue in the documentation of the <svn> task: http://nantcontrib.sourceforge.net/release/0.91/help/tasks/svn.html and I am not willed to waste my spare time on GitHub! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3527410&group_id=54790 |
|
From: Ryan B. <rm...@gm...> - 2012-05-07 03:34:05
|
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 nan...@li.... 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 |
|
From: Ryan B. <rm...@gm...> - 2012-04-23 04:54:42
|
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 nan...@li.... 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 |
|
From: Ryan B. <rm...@gm...> - 2012-04-16 05:20:04
|
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 <rm...@gm...> 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 |
|
From: Ryan B. <rm...@gm...> - 2012-03-22 00:11:55
|
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 |
|
From: Ryan B. <rm...@gm...> - 2011-12-06 06:28:07
|
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 |
|
From: Ryan B. <rm...@gm...> - 2011-11-14 06:56:06
|
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 |
|
From: Ryan B. <rm...@gm...> - 2011-11-12 01:59:09
|
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 <rm...@gm...> 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 <rm...@gm...> 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 (<sfusername>@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 >> > |
|
From: Ryan B. <rm...@gm...> - 2011-11-09 05:39:41
|
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 <rm...@gm...> 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 (<sfusername>@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 > |
|
From: Ryan B. <rm...@gm...> - 2011-11-05 23:53:54
|
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 (<sfusername>@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 |
|
From: Ryan B. <rm...@gm...> - 2011-10-23 03:45:48
|
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 nan...@li.... 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 |
|
From: SourceForge.net <no...@so...> - 2011-09-25 19:31:41
|
Patches item #1648001, was opened at 2007-01-30 16:15 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474853&aid=1648001&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Hadrian (honkster) Assigned to: Nobody/Anonymous (nobody) Summary: VB6 Task fails to rebuild projects with designers Initial Comment: If you have a VB6 project containing source files produced by designers, i.e. Reports, the file extention is .Dsr and when changed won't get recompiled. When parsing the VB6 project file the VB6 task does not check for source code that comes from a designer. I have added an extra check to the case statement in the method ParseProjectFile of VB6Task.cs so that .Dsr files will be included as source code and therefore will be rebuilt if they are changed. Hadrian ---------------------------------------------------------------------- >Comment By: Dominik Guder (dogu) Date: 2011-09-25 21:31 Message: added to 0.91 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474853&aid=1648001&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-09-25 19:26:30
|
Bugs item #1205594, was opened at 2005-05-20 13:57 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1205594&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: 0.85 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: olivier anguenot (oanguenot) Assigned to: Nobody/Anonymous (nobody) Summary: VB6 task not taking into account resource file Initial Comment: Hello, I use a <vb6> tasks in my nant build file. I want to compile a vbp project witch contains a reference to an external resource PhoneRes.res". In the vbp file, there is the line : ResFile32="PhoneRes.res" But when the file Phoneres.res is updated, the project is not recompiled. So, how can I force my vbp project to be compiled ? Thanks. Olivier ---------------------------------------------------------------------- >Comment By: Dominik Guder (dogu) Date: 2011-09-25 21:26 Message: Take "ResFile32" files into account when checking for recompilation. ---------------------------------------------------------------------- Comment By: Gert Driesen (drieseng) Date: 2006-01-17 21:09 Message: Logged In: YES user_id=707851 Can you please attach a small VB6 project (including sources) that contains a resource file to this bug report (or send it to me by email) ? ---------------------------------------------------------------------- Comment By: Giscard (giscard) Date: 2006-01-16 04:15 Message: Logged In: YES user_id=1428237 Edit the file NAnt.Contrib.Tasks... 1) protected bool ProjectNeedsCompiling(string projectFile) : Needs to be updated. There's a big conditional branch there starting with this code: "if (key == "Class" || key == "Module") {". Add an if/else for your "ResFile32" key, and inside the brackets make it store the value for that key. 2) protected bool ProjectNeedsCompiling(string projectFile) : Needs to be updated too. Here, find the comment "// look for a changed project file." This part of the code checks the project file, source files, and project references. Add similar four lines to compare the timestamp of the file in the private instance var you created in step 1. ---------------------------------------------------------------------- Comment By: Dominik Guder (dogu) Date: 2005-06-16 12:03 Message: Logged In: YES user_id=437335 Hi, I took a short look into and it seems that only class and module files are checked for actuality. But there are some more filetypes like ResFile32. Here I found a list of VB Project Filetypes http://www.vbaccelerator.com/home/VB/Utilities/VBPZip/VBPZip_Source_Code_zip_cVBFileTypes_cls.asp maybe some could take a closer look into so far Dominik ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1205594&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-09-25 19:15:16
|
Bugs item #1081472, was opened at 2004-12-08 17:56 Message generated for change (Settings changed) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: 0.85 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Hani Atassi (haniatassi) Assigned to: Nobody/Anonymous (nobody) Summary: vb6 task problems with Auto Increment revision Initial Comment: If the VB6 project set to "Auto Increment" the revision number of the version, the task <vb6> compiles the project each time even if it's up-to-date. This is because VB actually update the revision number after it builds the output file. So, the VB project file is always newer.. I fixed this temprorary by touching each output file that the compiler generates after a successful build. I am not sure if there is a better fix.. Thanks, ---------------------------------------------------------------------- Comment By: Dominik Guder (dogu) Date: 2011-09-25 21:14 Message: I added "compiledproptery" which defaults to vb6.compiled to nantcontrib 0.91 ---------------------------------------------------------------------- Comment By: Giscard (giscard) Date: 2006-01-16 04:27 Message: Logged In: YES user_id=1428237 I had the same problem. I solved it similarly, except I edited the code for the vb6 task so that it updates the timestamps of the files it builds after the .vbp get's updated with the new version number. This way you don't have to remember to add a call to touch in the nant scripts, and it doesn't break anything in the case where you aren't using auto-increment. ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 18:17 Message: Logged In: YES user_id=590187 Yes Gert, I think it's very important to extend uptodate to use project and solution files, so it would tell us if they are uptodate or not. But still this won't fix the VB problem, because VB touches the project file after a succefull build if "Auto Increment" options is set. Uptodate could be useful in case of manuallly increasing the build number in VB project, but not when Auto Increment option is turend on. ---------------------------------------------------------------------- Comment By: Gert Driesen (drieseng) Date: 2004-12-10 17:38 Message: Logged In: YES user_id=707851 Yeah, we should give it some more thought. I guess we could introduce an interface that tasks that support a "needscompiling" mechanism could implement. We could then extend the <uptodate> to work with these tasks. I'm just thinking out loud here (after having a few glasses of wine), so it might not make much sense ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 17:22 Message: Logged In: YES user_id=590187 Another solution would be to set a property to true if the vb project was compiled.. Something like this would be added after a call to ExecuteTask(): Project.Properties["vb6.compiled"] = "true"; and set the same property to false before NeedsCompiling(). In this case i can test for vb6.compiled in my NAnt script and touch the outfile if necessary.. I wonder if this could be a benifit to add to other NAnt tasks like the solution task.. It's a good indecator to inform back the script that the solution was compiled or wasn't because it was uptodate.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-09-25 19:14:49
|
Bugs item #1081472, was opened at 2004-12-08 17:56 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hani Atassi (haniatassi) Assigned to: Nobody/Anonymous (nobody) Summary: vb6 task problems with Auto Increment revision Initial Comment: If the VB6 project set to "Auto Increment" the revision number of the version, the task <vb6> compiles the project each time even if it's up-to-date. This is because VB actually update the revision number after it builds the output file. So, the VB project file is always newer.. I fixed this temprorary by touching each output file that the compiler generates after a successful build. I am not sure if there is a better fix.. Thanks, ---------------------------------------------------------------------- Comment By: Dominik Guder (dogu) Date: 2011-09-25 21:14 Message: I added "compiledproptery" which defaults to vb6.compiled to nantcontrib 0.91 ---------------------------------------------------------------------- Comment By: Giscard (giscard) Date: 2006-01-16 04:27 Message: Logged In: YES user_id=1428237 I had the same problem. I solved it similarly, except I edited the code for the vb6 task so that it updates the timestamps of the files it builds after the .vbp get's updated with the new version number. This way you don't have to remember to add a call to touch in the nant scripts, and it doesn't break anything in the case where you aren't using auto-increment. ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 18:17 Message: Logged In: YES user_id=590187 Yes Gert, I think it's very important to extend uptodate to use project and solution files, so it would tell us if they are uptodate or not. But still this won't fix the VB problem, because VB touches the project file after a succefull build if "Auto Increment" options is set. Uptodate could be useful in case of manuallly increasing the build number in VB project, but not when Auto Increment option is turend on. ---------------------------------------------------------------------- Comment By: Gert Driesen (drieseng) Date: 2004-12-10 17:38 Message: Logged In: YES user_id=707851 Yeah, we should give it some more thought. I guess we could introduce an interface that tasks that support a "needscompiling" mechanism could implement. We could then extend the <uptodate> to work with these tasks. I'm just thinking out loud here (after having a few glasses of wine), so it might not make much sense ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 17:22 Message: Logged In: YES user_id=590187 Another solution would be to set a property to true if the vb project was compiled.. Something like this would be added after a call to ExecuteTask(): Project.Properties["vb6.compiled"] = "true"; and set the same property to false before NeedsCompiling(). In this case i can test for vb6.compiled in my NAnt script and touch the outfile if necessary.. I wonder if this could be a benifit to add to other NAnt tasks like the solution task.. It's a good indecator to inform back the script that the solution was compiled or wasn't because it was uptodate.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-08-23 07:00:41
|
Patches item #3049924, was opened at 2010-08-21 05:17 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474853&aid=3049924&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Ryan Boggs (rmboggs) >Assigned to: Dominik Guder (dogu) Summary: File Function Test Fix Initial Comment: The hash values listed in the FileFunctionsTest.cs are incorrect and prevents NAntContrib from completely building. The attached diff corrects the tests and builds fine with the latest version of NAnt (0.91 Alpha2) ---------------------------------------------------------------------- >Comment By: Dominik Guder (dogu) Date: 2011-08-23 09:00 Message: Fixed end of May 2011 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474853&aid=3049924&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-08-22 22:02:32
|
Bugs item #1745360, was opened at 2007-06-29 16:21 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1745360&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Tasks Group: 0.85 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Gilles HERRGOTT (gihe) >Assigned to: Dominik Guder (dogu) Summary: VB6 Task Typelib vbscript.dll does not exist Initial Comment: Hi, We have a reference to vbscript.dll like below in a project file : Reference=*\G{3F4DACA7-160D-11D2-A8E9-00104B365C9F}#5.5#0#C:\WINDOWS\system32\vbscript.dll\3#Microsoft VBScript Regular Expressions 5.5 During the compilation task processed by VB7 Task Nant Contrib, the warning below is displayed: [vb6] Type library file 'C:\WINDOWS\system32\vbscript.dll\3' does not exist. The '\3' is a reference to a specific type lib. How can we disable the warning message or correct that ? Thanks in advance for your support. Cordially, Gilles ---------------------------------------------------------------------- >Comment By: Dominik Guder (dogu) Date: 2011-08-23 00:02 Message: Fixed today ---------------------------------------------------------------------- Comment By: Gilles HERRGOTT (gihe) Date: 2007-06-29 17:22 Message: Logged In: YES user_id=1269205 Originator: YES Patch proposed: // Check if file exists, if type lib contains multiple interfaces, drop the interface reference if (File.Exists(tlbName) || (File.Exists(tlbName.Substring(0,tlbName.Length-2)))) { references.Includes.Add(tlbName); } else { Log(Level.Warning, "Type library file '{0}' does not exist.", tlbName); } ---------------------------------------------------------------------- Comment By: Gilles HERRGOTT (gihe) Date: 2007-06-29 17:00 Message: Logged In: YES user_id=1269205 Originator: YES TypeLib references are stored in the registry \\HKEY_CLASSES\ROOT. The key \5.5\0\win32 ref the "C:\WINDOWS\system32\vbscript.dll\3" dll. The reference is checked during the build process. The task cannot the file in the directory "c:\windows\system32". That's ok and does'nt break the compilation process. Do you know also a way to process the '\3' string in order to allow the task to find the file and not display this warning ? (File vb6Task.cs line 525) Thanks for your support, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1745360&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-08-18 21:50:54
|
Bugs item #3214616, was opened at 2011-03-16 01:35 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3214616&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Pavel Chuchuva () >Assigned to: Dominik Guder (dogu) Summary: msbuild task should not put quotes around /target parameter Initial Comment: This prevents specifying multiple targets separated by semicolon, see http://msdn.microsoft.com/en-us/library/ms164311.aspx ---------------------------------------------------------------------- >Comment By: Dominik Guder (dogu) Date: 2011-08-18 23:50 Message: Fixed this issue. Only targets with space are surrounded with quotes separately ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3214616&group_id=54790 |
|
From: SourceForge.net <no...@so...> - 2011-03-16 00:35:40
|
Bugs item #3214616, was opened at 2011-03-16 11:35 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3214616&group_id=54790 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pavel Chuchuva () Assigned to: Nobody/Anonymous (nobody) Summary: msbuild task should not put quotes around /target parameter Initial Comment: This prevents specifying multiple targets separated by semicolon, see http://msdn.microsoft.com/en-us/library/ms164311.aspx ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=3214616&group_id=54790 |
78 messages has been excluded from this view by a project administrator.