Hello, simply adjust the Version in "build-package.bat" and run that file. After a successful build you'll find the resulting binaries in the "/Publish" dictionary.
Daniel On 23.05.2012 18:03, Madhav Ponugoti wrote: > Hi All, > > I would like to create a new > "CruiseControl.NET-CCTray-1.6.7981.1-Setup.exe" so that the source > code changes i made are reflected on CCTray. How to build a new > "CruiseControl.NET-CCTray-1.6.7981.1-Setup.exe" file so that all the > users who install the CCtray from Dashboard will have my changes. I > made changes to 'Remote' Package of the 'ccnet' solution. > > Thanks and Regards, > Rao. > > On 5/14/12, Madhav Ponugoti <[email protected]> wrote: >> Thanks for the reply Dan. I will try exchanging the assemblies first before >> trying to rebuild the installer. >> >> The changes i made are very minor, i made changes to WebDashboard assembly. >> We have multiple physical build machines were the build is fired onto, i >> wanted to display the machine names and their availability information on >> the Dashboard, so changed couple of class files and one vm file to >> accomplish this. >> >> Thanks, >> Rao. >> >> On Fri, May 11, 2012 at 5:22 PM, Daniel Hommel <[email protected]> wrote: >> >>> Hi Rao, >>> >>> regarding your question two things come to my mind: >>> >>> 1. The answer to your question: You can just exchange the assemblies or >>> build the installer aswell (there is a target for it in the build >>> script) and reinstall using your custom made installer (be sure to >>> backup your artifacts and state files before uninstalling as the >>> uninstall process might remove them otherwise). >>> >>> 2. A question regarding your changes: What have you changed? Is it >>> something others might benefit from? Do you mind sharing it? >>> >>> Best regards, >>> >>> Daniel >>> >>> >>> On 05/11/2012 11:37 PM, Madhav Ponugoti wrote: >>>> Hi All, >>>> >>>> I have downloaded CCNET 1.6.798.1 source code and made some custom >>>> changes for our build purpose. Now i want to install the changes made >>>> to our build machine as we usually do with the standard install. How >>>> to accomplish this? >>>> >>>> Really appreciate any direction on this. >>>> >>>> Thanks, >>>> Rao. >>>
