Fervent Coder

Coding Towards Utopia...by Rob Reynolds
posts - 278 , comments - 431 , trackbacks - 0

My Links


Rob Reynolds

Subscribe to Fervent Coder RSS
Subscribe to Fervent Coder by Email

About Me

I manage several open source projects. Need...
   ...package management for Windows?
   ...automated builds?
   ...database change management (migrations)?
   ...your application to check email?
   ...a monitoring utility?

I also write for

Like what you are reading? Want to buy me a cup of coffee?
PayPal - The safer, easier way to pay online!


Post Categories


UppercuT - Automated Builds - Getting Started Part 6 (Source Control & What NOT to Check In)

In Part 1 we downloaded or built from source control. In Part 2 we added UppercuT to our project. In Part 3 we set up the UppercuT configuration. In Part 4 we updated our reference folders if we needed to. In Part 5 we built our code successfully. Now we are ready get this into source control. Let's UppercuT our code!


Artifacts of the Build

UppercuT outputs some files and folders that should never be checked into source control. These are basically the same as what is in your bin directories with some differences. These folders/files should be excluded from source control.



The build_output folder is like the bin folder, but it’s the bin folder that puts every project in the solution’s output in this folder. Why not call it bin? We didn’t want to interfere with those projects that might have a top level bin folder.


The code_drop folder is the nice packaging of the built application so that it is ready for deployment. Why code_drop? That’s a great question. The answer is that we had a lot of thoughts about what to call it, but in the end, code_drop seemed to make sense so we came back to it.


The SolutionVersion file is the file that changes with every build. It puts into it all of the common assembly elements. You can reference this file (using a link - see VersionBuilder) in every project and get the benefit of automatic versioning of your DLLs. If you are not using subversion or a continuous integration server, you can still get benefits of all of the other common elements by using the SolutionVersion file.

NOTE: A Visual Studio build will not work without SolutionVersion present (build.bat has been run at least once). Some people find it easier to go ahead and check that in on OSS projects to reduce the amount of confusion.


Check it In

Once we are building successfully, we need to get our changes updated in source control. NOTE: This is based on Subversion.

1. Open a commit dialog. Do not check in unversioned files. We have some files/folders that we don’t want to check in that are artifacts of the build.


2. We make sure {Show unversioned files} is unchecked. Click {OK}.


 UppercuT - Getting Started Series

Part 0 - Prerequisites
Part 1 - Get UppercuT
Part 2 - Add UppercuT to your project
Part 3 - Configure UppercuT.config
Part 4 - A note about the external tools / libraries
Part 5 - Build It!
Part 6 - Source Control / What NOT to check in
Part 7 - Setting up TortoiseSVN to Globally ignore UppercuT output folders and files
Part 8 - Next Steps

With this knowledge you shall build.

kick it on DotNetKicks.com

Print | posted on Saturday, May 30, 2009 7:35 AM | Filed Under [ Code UppercuT ]


Comments are closed.
Comments have been closed on this topic.

Powered by: