build-process

We have a project in Visual Studio 2010 that runs a batch file in the post-build event. That batch calls to signtool.exe from Microsoft SDK to sign and timestamp the binary. Timestamp servers (we use http://timestamp.verisign.com/scripts/timstamp.dll ), however, tend to be unreliable for some reason, failing sometimes. This caused build to fail. We implemented a more advanced batch script then (based on this code), splitting signing and timestamping, and allowing to retry the timestamp operation, if it failed. Here is a simplified version of the batch script (signfile.bat): @echo off REM sign

A beginner question, bear with me: I'm just wondering under what circumstances one should use a build tool like nant or msbuild? I'm working on a medium sized application (.net 3.0), every developer is doing his work and builds on his machine checking his code changes into the repository as he goes. Once we're all done, I'll get all the code from the repository, make a clean build on my machine and we deploy the binaries. Just out of curiosity, where comes the build tool in? The short answer is always. Each developer should be building using the build script before checking code in. The people

Our build is annoyingly slow. It's a Java system built with Ant , and I'm running mine on Windows XP. Depending on the hardware, it can take between 5 to 15 minutes to complete. Watching overall performance metrics on the machine, as well as correlating hardware differences with build times, indicates that the process is I/O bound. It also shows that the process does a lot more reading than writing. However, I haven't found a good way to determine which files are being read or written, and how many times. My suspicion is that with our many subprojects and subsequent invocations of the compiler

Using Coffeescript I need to have a go through a build script anyway to update my .js files, and I have two of them, one for debugging and one for production (one uses Uglify to minimize the files, one does not). So I was thinking that it would be convenient to have some conditional compilation as well, with code that only enters the debug build. What is the easiest way to achieve this, ideally controlled by a simple command line switch that I can give to either coffee or uglify? If you're writing a build script anyway, you can add a preprocessor step to it. Since CoffeeScript uses # to denote

I'm setting up CruiseControl.NET and during the build I want to modify my version.txt file and have it checked in. When I do this, CruiseControl.NET doesn't know this checkin was done by the build and so the next time it checks sources, it sees there were modifications and rebuilds again (I have IfModificationExists set in the project build). How do I tell CruiseControl.NET to check this file in or let it know that this one is OK so it doesn't keep re-triggering builds? g . You can use exclusionFilters in the project to exclude the version.txt file from triggering a build. <sourcecontrol type=

I have a solution file comprising of 15 projects using a few third party dll references. I want to be able to build the solution from a batch file. What is the best way to do this? Thanks Run msbuild - for example: msbuild MySolution.sln /p:Configuration=Release /p:Platform="Any CPU" One of the simplest ways is to execute msbuild with the solution file as input: @echo off call %windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe path\to\solution.sln If this is done in a Visual Studio command prompt you can skip the path to msbuild.exe. One way to get started is to open the project in Visual

I have a few Visual Studio Solutions/Projects that are being worked on in my company, which now require a scheme for automatic nightly builds. Such a scheme needs to be able to check the latest versions from SVN, build the solutions, create the appropriate downloadable files (including installers, documentation, etc.), send e-mails to the developers upon errors and all sorts of other nifty things. What tool, or tool-set, should I use for this? I used to use FinalBuilder a few years ago and I liked that a lot but I'm not sure if they support such features as nightly-builds and email messages.

We've had an ongoing need here that I can't figure out how to address using the stock Maven 2 tools and documentation. Some of our developers have some very long running JUnit tests (usually stress tests) that under no circumstances should be run as a regular part of the build process / nightly build. Of course we can use the surefire plugin's exclusion mechanism and just punt them from the build, but ideally we'd love something that would allow the developer to run them at will through Maven 2. Normally you would add a profile to your maven configuration that runs a different set of tests: