Giscard, I would agree 100% that the mechanism you describe is what *should* happen. In fact, Our current solution does something almost identical... only it uses gnu make (instead of NNnt), plus a couple of custom utilities. As I'm sure you will appreciate, the output from make is less web-presentation-friendly than Nant. :-)
Unfortunately, speaking from experience, there have been times when the compatibility files were not appropriately updated in source code control (including one occasion when Visual Source Safe did something utterly bizarre with the file), and it has been necessary to perform exactly the type of manual intervention you describe in a local build (updating the binary compatibility files), before committing the entire change set back. Thanks for the links to your blog. I think management would be very interested in a more graphical view of the project we inherited (and any future ones we may inherit). You may be getting more questions from me soon! :-) Regards, Richard -----Original Message----- From: Giscard Biamby [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 26, 2006 22:39 To: Foster, Richard - PAL; nant-users@lists.sourceforge.net Subject: RE: [NAnt-users] Building VB6 project group The method I use for my vb6 projects is a little different. I will take a look at the thoughworks page to see if some of their vb6 tools could help me. My method only builds the .dll's once. [Remainder of message trimmed] ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
