Gregory A. Lusk wrote:
/I have two VS.NET solutions that I are built using NAnt and
CruiseControl.NET. Several projects in the second solution are
dependent upon assemblies that are outputs from the first project. I
need to automatically update the references for the second solution up
to date whenever a successful build of the first solution occurs. I’ve
tried simply copying the newly-compiled assemblies from the first
solution into the directory where the second solutions references are
stored, but when the version numbers change the assembly manifest no
longer matches the project reference. Furthermore, this doesn’t keep
my subversion repository up to date, and I don’t get the latest
references whenever I check out the second project./
/ /
/Should I just use static version numbers and only increment the
revision number? And is there a command that I can use to check in the
newly-compiled assemblies from the first solution?/
/ /
I'd go with static version numbers, but I think I'd first look at
merging them into one solution. If they really don't belong in one
solution, then I'd ask whether the second solution really needs the
latest build of the first.
You didn't say what version control system you're using. There are NAnt
tasks for some systems but not all. However, it's not really common to
check in newly compiled assemblies from frequent builds.
Gary
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
