It's probably clear, but did forget to mention that to use this, you add this project to your solution and then configure your solution to turn off building for all projects except this one. The benefit from my perspective (a minor one) over the External Tool approach that some people use is that the existing Build / Rebuild functions continue to work for the solution and that build errors show up in the normal build errors task list instead of only in the Output window.
-----Original Message----- From: Erv Walter [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2003 11:56 AM To: Tomas Restrepo; [EMAIL PROTECTED] Subject: RE: [nant-dev] Solution/Project Parser In the event that this is useful to others, I have attached the project we use to make VS.NET 2003 "integrate" with NAnt. It's a VS.Net 2003 C++ "Makefile" project. The way it works is that you can configure a makefile project to call whatever command you want to do the actual build. Interestingly, you will still get good VS.NET integration for any build errors. This is because NAnt uses csc.exe to do the build and VS.NET apparently understands how to parse the csc.exe error output. In order to get debugging to work (for a windows exe or console app), you will need to hand tweak 2 settings in the NantBuilder project properties. On the debugging tab, you need to set these: Command: $(SolutionDir)build\YourOutput.exe Working Directory: $(SolutionDir)\build\ For some stupid reason, these will be stored for you in the .suo file (which is why you have to do them yourself). Obviously, replace "YourOutput.exe" with whatever the name of your debugable executable is. For all of the above, you may need to make some adjustments based on how you have NAnt configured to build. The above depends on: - Nant.exe being in Tools\NAnt subdirectory of your solution (a convention that we use internally) - default.build being in your solution directory - build, rebuild, and clean targets in your default.build directory - all of your build output going into a build\ subdirectory of your solution If you have a different NAnt setup, you'll need to adjust the project accordingly. You also might be able to set something up similar in VS.NET 2002, but I have never tried. Maybe I'll see if I can figure out how a Wiki works and then add this information there. Enjoy, Erv -----Original Message----- From: Tomas Restrepo [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2003 11:32 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] Solution/Project Parser 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