Our team has recently completed a similar migration. nant is our "build system of record", however it's also convenient to develop and build parts of the project in Visual Studio. We're all Java heads, so Visual Studio artifacts anger and confuse us. Here's what we've done to keep the disparate build environments from tangling:
* Configure nant and VS.NET such that one compiles 'release' builds and the other 'debug'. This will avoid .PDB locking conflicts between the two environments. * After adding your lib references in VS.NET, close the project, open the project file in a text editor, and confirm the references have relative paths (for .csproj sharing purposes) * Don't run Windows Services, ASP.NET, or forms applications in place: `<copy/>` them somewhere first, lest the resources be locked Those idiosyncrasies aside, most traditional ant practices port well. Enjoy, /Justin -----Original Message----- From: Nau, Michael [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 06, 2003 9:49 AM To: [EMAIL PROTECTED] Subject: [Nant-users] nAnt Best Practices Can anyone provide some feedback as to best practices for using nAnt. How are the projects normally setup? How are dependencies normally managed? We are exploring converting our java / j2ee components to c# / .NET and I am in charge of setting up the build environment. Any advice would be greatly appreciated. Thanks, Mike. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld =omething 2 See! http://www.vasoftware.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
