Kelly, I don't know what your build structure is, but I have certainly come across similar problems in the past. One of teh reasons for switching to NAnt originally was the problem with VS using hint paths and if it couldn't find a referenced assembly, it goes and looks for something similar.
My prefered solution to this is that I don't rely on anything being installed on the build machine. Any assemblies/dlls/libraries that are required are stored in a "references" folder along with the source for the solutions and are referenced from there by the vs project files, and also the NAnt build scripts. that way you can guarentee that you are building against the version you want to rather than whatever someone has installed on their machine. It also makes it easier to include the files in your install set as you know where to find them (I normally keep third party .msm's in there too) and it means you don't have any relience on every developer havng the same hard disk layout so that relative paths to c:\WINNT etc work correctly. Cheers, Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anderson, Kelly Sent: 22 September 2005 18:47 To: nant-users@lists.sourceforge.net Subject: [Nant-users] Configuration Management One of the major problems we have with our current (non-NAnt) build system is that it is dependent upon various libraries and programs being installed just so on your computer. You can build the application on one computer, but it may not work on another computer. Same source files, different results due to things outside the build system. As one little example of what I'm talking about, our code uses an older version of DirectX, and if you install the current version, bad things happen. Of course Windows and other programs are always trying to update you to the current version... Have any of you used NAnt to install groups of programs and libraries onto a fresh machine to make sure it's in a good state for building the application? Do you have any knowledge of any pitfalls to avoid? Should this be separate from or part of your normal build process? Should checking the state be part of the build process? Can that be done fairly easily? Is this an entirely stupid approach, and would something like virtual machines be a better way to approach this problem in general? Am I looking at all my problems as nails with NAnt being my new hammer? :-) -Kelly E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
