[nant-dev] Nested build example
Attached is an example of using nested build files. This example closely follows how we organise our build files here. I am not certain that it is the best way, and would be open to suggestions on better techniques. Creating this example has made me consider the whole topic of 'NAnt Best Practices'.. but that can wait for another day. -MG Nested.zip Description: Zip compressed data
Re: [nant-dev] Next release
I agree with Dave, documentation needs to be addressed. I really like the Wiki idea. We used a Wiki for documentation on my last project with good success. Our customer resisted it at first our original idea was to get the users to help with the documentation by editing the pages. It was accepted as a documentation medium when we showed that we could have an admin user that allowed us to edit the documentation and not allow the users to alter it. We gave our user base a separate forum for adding notes, requests and communication amongst themselves. shameless_plug I'd be willing to take a look at deploying a wiki to my NCode Sourceforge project to see if it works. NCode is a VS.Net IDE Add-In that does code completion from live templates (just like IntelliJ if anyone has used that). urlncode.sourceforge.net/url /shameless_plug -Aaron -Original Message- Message: 9 Date: Thu, 6 Feb 2003 07:44:23 -0500 From: Dave Sanders [EMAIL PROTECTED] ... Documentation. Specifically I've had to spend a lot of time just playing with it and seeing what it does. ... Have you considered hosting a Wiki for keeping and maintaining documentation? Even if you kept it hidden away for the developers list, and published out static files as the documentation - it would be a quick and easy way for all of us to contribute little snippets of information without any one person or group of people having to write full documentation. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Next release
Quoting Tomas Restrepo [EMAIL PROTECTED]: That sounds like a great idea. Scott, what do you think? If there's any problem with getting it on the sourceforge servers, I'd be willing to share some space on my hosting (provided we find a wiki we can run there). I'm using PureEnergy hosting for mine: http://www.purenrg.com/. $6 a month, runs on linux and has a lot of good features. This is where I've set up TWiki for my site. If you want a microsoft based wiki, you can go look here http://www.openwiki.org/ - not as full featured as others, but it works well. Or, find a huge lists of wiki's here: http://www.purenrg.com/ - the Original Ward Cunningham wiki. There are some dotNET ones, but I haven't had good luck with them - mainly they don't have a lot of features, or they aren't done and aren't showing progress. D --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAnt Wiki
Awiki sounds like a great idea. I'm all for it. I will set one up at http://NAnt.Sourceforge.Net/wiki later today. As for content, it seems like user guides and best practices docsare probably what will be most useful. I don't think that the task references should be maintained in the wiki. I'd like to see the source code comments stay the sourcefor the documentation of the task references. It seems like this would be the best place to keep that kind of information. But I'm open to see what happens. I don't want to push anything, but from my experience, it seems like task refs are probably left out ofwiki type documentation.
Re: [nant-dev] Next release
Sansone, Aaron wrote: shameless_plug I'd be willing to take a look at deploying a wiki to my NCode Sourceforge project to see if it works. NCode is a VS.Net IDE Add-In that does code completion from live templates (just like IntelliJ if anyone has used that). urlncode.sourceforge.net/url /shameless_plug looks good Aaron. Did you copy the NAnt home page ? It still says NCode - A .NET Build Tool in the title :) Ian -Original Message- Message: 9 Date: Thu, 6 Feb 2003 07:44:23 -0500 From: Dave Sanders [EMAIL PROTECTED] ... Documentation. Specifically I've had to spend a lot of time just playing with it and seeing what it does. ... Have you considered hosting a Wiki for keeping and maintaining documentation? Even if you kept it hidden away for the developers list, and published out static files as the documentation - it would be a quick and easy way for all of us to contribute little snippets of information without any one person or group of people having to write full documentation. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Nested build example
Mark, This has been my approach as well. Have a .build file at a given directory level be responsible for building itself and nested subdirectories. I would often have a common .build file that contains common propeties that all the other .builds would include. Ian Attached is an example of using nested build files. This example closely follows how we organise our build files here. I am not certain that it is the best way, and would be open to suggestions on better techniques. Creating this example has made me consider the whole topic of 'NAnt Best Practices'.. but that can wait for another day. -MG --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
