Thanks for the reply Dan. I tried building it the way you have suggested, but got below error.
[msbuild] CopyFilesToOutputDirectory: [msbuild] CCNet.CSharpDemos.Plugin -> C:\Users\ADBuilder\Desktop\CruiseControl.NET-1.6.7981.1.source\project\CCNet.CSharpDemos.Plugin\bin\Release\CCNet.CSharpDemos.Plugin.dll [msbuild] Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5". [msbuild] vbc : Command line error BC2026: warning number '42353' for the option 'nowarn' is either not configurable or not valid [msbuild] vbc : Command line error BC2026: warning number '42354' for the option 'nowarn' is either not configurable or not valid [msbuild] vbc : Command line error BC2026: warning number '42355' for the option 'nowarn' is either not configurable or not valid BUILD FAILED C:\Users\ADBuilder\Desktop\CruiseControl.NET-1.6.7981.1.source\ccnet.build(111,4): External Program Failed: C:\Windows\Microsoft.NET\Framework\v3.5\msbuild.exe (return code was 1) ** I checked online at the below link for resolution, but i was not able to find 'Compile Tab' under Project properties in VS2010. http://stackoverflow.com/questions/2803681/problems-upgrading-vb-net-2008-project-into-vs2010 Thanks, Rao On 5/24/12, Daniel Nauck <[email protected]> wrote: > 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. >>>> >
