tag:blogger.com,1999:blog-60353959470934127912011-08-19T02:29:24.975-05:00Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.comBlogger81100tag:blogger.com,1999:blog-6035395947093412791.post-77641682854523697712007-06-18T19:40:00.001-05:002007-07-12T09:27:05.909-05:00

With a Subversion server functioning and a project loaded, it is time to install CruiseControl.Net and configure it to access the Subversion project in source control (Part 1), automate build tasks using MSBuild (Part 2) and finally look at the optional CruiseControl.NET configuration options that are of interest (Part 3).From here on I'll be using a real project I have published on my public

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-71926286963020273602007-04-18T18:46:00.000-05:002007-04-18T19:16:06.806-05:00

Picking up from yesterday, the trunk is now loaded with the source for a preexisting project. However, the structure we have now locally under Subversion Repositories is not ideal to work with in Visual Studio. The main problem is that the arrangement can make switching between the trunk, branches, and tags a hassle. Pulling a branch or tag under trunk then accidentally committing can be annoying

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-82751606779736658132007-04-17T20:14:00.000-05:002007-04-17T21:50:25.027-05:00

In two days I have installed Subversion and TortoiseSVN, set up a Subversion windows service to host multiple repositories, planned a repository structure and created the initial structure in a new repository. Not really a lot of work to speak of, but I'm taking my time. Now I am going to load an existing Visual Studio 2005 project into the waiting repository.Before loading the existing code into

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-14280143913234599072007-04-16T21:48:00.000-05:002007-04-17T21:51:06.436-05:00

I have a newly created, configured and empty subversion repository tritely named {MyRepository}. I have put some time into planning the initial structure to meet my needs and am ready to initialize {MyRepository} using TortoiseSVN on a workstation running Windows XP Pro. The following instructions assume you are using Windows Explorer to setup the folder structures.HousekeepingFirst, create a new

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-83901429780768007632007-04-16T18:01:00.000-05:002007-04-16T19:47:57.165-05:00

The first thing to do before populating a repository is to plan out the structure. While Subversion has a decent set of functions for restructuring the contents of a repository, don't be forced to try them out due to poor planning. Avoid an unnecessary headache by thinking about the structure before committing the first file.The documentation for Subversion and TortoiseSVN recommend using the

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-60057620058029412152007-04-15T20:15:00.000-05:002007-04-16T18:36:56.958-05:00

I have decided I need to run multiple Subversion repositories under the same windows service. My original train of though was that I would just use a single repository and create a folder for each project off of the root. After reading a bit more, I found two facts that would make this kind of implementation distasteful:I want to be able to expose and share certain projects with my friends, but I

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0tag:blogger.com,1999:blog-6035395947093412791.post-91805920667274188892007-04-15T19:19:00.000-05:002007-04-16T18:41:32.500-05:00

Getting Subversion running seems to be the best place to start; a good version control system is a cornerstone of any solid development and build environments. In addition to the server, I need to install and configure the client software and start moving my source code into the new repository.I have used Subversion clients to access a few Open Source projects in the past, and played around with

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com6tag:blogger.com,1999:blog-6035395947093412791.post-28054056138699384082007-04-15T14:37:00.000-05:002007-06-18T19:39:52.970-05:00

I recently decided to revamp my build environment for .NET development. Aside from my day job, I do a lot of hobby development at home on a variety of projects. Up to this point I have been using a "poor man's" system of zip files for version control, NUnit for unit tests, and NDoc for documentation. I need to start using version control consistently and want to integrate an automated build/test

Brandon Haasehttp://www.blogger.com/profile/06405091999875532871noreply@blogger.com0