Hi there, I'm totally new to NAnt, but am looking to develop a solution and I'm hoping someone may have some initial pointers. I've just taken over the role of config management on a project and I'm looking to replace the existing VB script and command line solution with something a little more predictable/reliable/configurable. The overall client solution is in C# (.NET 2003 / 1.1), housing about 8 or so projects. In short, we deploy the application to two device types:
1. Handheld (CE) 2. Laptop/Desktop (Win32) in three environments: 1. Debug 2. Link Test 3. System Test in two releases: 1. Debug 2. Release Possibly more in future, but once I've got a steer on these any extensions should be fairly straight forward. At present we go through the following steps: 1. Delete any existing code/builds in our target folder 2. Label all source code in Version Manager to signify a build is in progress 3. Get all source code from Version Manager and copy to our target folder 4. Search Version Manager for AssemblyInfo files, check these out and amend 5. Edit the local copies of the AssemblyInfo files to reflect the newly calculated build number 6. Check these amended files back in 7. We then run a separate VB script that kicks off the build process, which consists of: 8. Define the solutions, configurations, source config files, target config files and test configurations 9. Call a build on solutions and test configurations, which gives us the two release builds for each of the 4 main solutions 10. Check the build log for errors 11. If successful, we then loop through the three environment types, putting a custom config file in place, calling a script to then copy and package up that environment to its own folder 12. Repeat for the remaining environments 13. Check the build log for errors 14. If successful, remove build label from Version Manager files 15. Build complete So................is this easily achievable in NAnt? One of the key problems at the moment lies with not being able to control or configure what we churn out. I want to set it up on a continual build process and be able to easily output a specific build if one source file changes that only impacts one project, rendering a full build a waste of time. One of our big bottlenecks here is getting all the code from PVCS. Most of the time, most of the code we get is unchanged. If there was a way to reduce this it would be awesome. Configurability would be excellent too. Being able to specify at run-time what I want would be superb. I've got a steep learning curve here, but that's fine with me! I am hoping that with NAnt that I can cut down on the amount of code we have at present. A lot of the problems are linked to it all being hard coded into the VBScript. If anyone in a similar position has any advice to offer it would be very welcome! Cheers, Mike. __________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __________________________________________________________________________ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
