I'm looking for "Best Practices" for components that are shared among several applications in reference to NAnt. First of all, dll or project references. If I have dll references, I have to get all of the developers to keep these components in the same place as I keep them for the build so that the hint path resolves. If I go with project references, I have to build the shared component inside of the same <solution> task as I'm building the application, correct? What I'd rather do is call a .build file for each of the shared components telling it what label to get the code from and where to put the assemblies when it compiles them. However, this only works for dll references because a project reference won't be able to resolve the GUID. Any advise would be very much appreciated, we're getting A LOT of shared components going and it's getting pretty confusing the way I'm doing it right now.
Thanks, Eric __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------------------------- 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&kid=120709&bid=263057&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
