My whole team does this all too. Here is the writeup I gave out a while back to the OT list on how to do this:
Here are the steps I used to integrate[note I do not address keeping a csproj in sync with the build file, but I could] Do this once: 1. Add an external tool Title: Nant (Current Project) Command: nant <-- assuming nant is in your path. Arguments: [I have nothing here, I use the default target in VS.NET] Init Dir: $(ProjectDir) I check Use Output Dir. This gives you output lines which are context sensitive for the file, line of the error/warning. 2. Add an external tool Title: Nant (Solution) Command: nant <-- assuming nant is in your path. Arguments: [I have nothing here, I use the default target in VS.NET] Init Dir: $(SolutionDir) Check Output Dir. 3. I have hooked up F7 to Nant (Current Project), and Shift-F7 to Nant (Solution) through the Keyboard settings in Tools|Options. For each project you want to use Nant: 1. Create a new build configuration called Nant(or whatever). Turn off building for all projects in this solution. 2. Switch to this Configuration. Then you can use F7 to build. And when you want to debug none of you projects will build since your configuration has them turned off. I could have had some tool do a transform on my project file into a build file. I believe there is a xsl out there to do this. This all has worked quite nicely for me. HTH -bc ---------- Original Message ---------------------------------- From: "Tomas Restrepo" <[EMAIL PROTECTED]> Date: Thu, 24 Jul 2003 11:31:33 -0500 >Matthew, > >> I'm also getting close to wanting to use NAnt completely within the >> build process. > >We do this for our project. We actually went a little bit further,and we >actually have a single VS.NET solution and project that *never* get built, >it's just for intellisense and the vs.net VSS integration ;) > >Every developer (the main dev team has about 8 people) builds directly with >nant everytime (one of my coworkers came up with the idea to add a custom >tool to vs.net that fires nant for the project and puts the nant output in >the vs.net output window. nifty!). > >No problems with this setup, really. The project is not too bit, though, >consisting of about 20 dlls or so, and 200.000+ lines of code, with a fairly >complex build and install process (for gac and COM+ registration). > >-- >Tomas Restrepo >[EMAIL PROTECTED] > > > >------------------------------------------------------- >This SF.Net email sponsored by: Free pre-built ASP.NET sites including >Data Reports, E-commerce, Portals, and Forums are available now. >Download today and enter to win an XBOX or Visual Studio .NET. >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >_______________________________________________ >nant-developers mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
