Committing and Updating

I have been using SVN for a few months now. I set up a private repository on a network drive and have been maintianing 3 different working copies from it.

I have figured out recently that i can check in (commit) multiple directories at once. This was important because i frequently have files across numerous directories that i want to check in or commit. I was doing these one directory at a time so the version number was too frequent.

We are planning to create a new shared "with security" repository for our main application. We will be dicussing best practices and commit policies. Being sure that when we commit to the *production repository, that we have tested and mature code. We need not be treating the production repository as a holding tank for development code. This is the way we used to use our old repository, we checked in early and often. While these is much merit to this process, it did contribute to a messy repository.

I will continue to use the repository that i created as a developer repository, but we need to create a shared developer repository, like the one that we have been using for many years. Our old repository had the ability to check in files, as opposed to directories or the entire repository. This worked well when multiple developers had there hands in the same areas.

I have a little problem synching up my working copies. some how two folders in my working copies go confused and was pointing to a different location. This was a problem for a couple reasons. 1st - when i would do an update, i would see files being removed and others being added when they should not have been. The source locations for the working copies go switched around. My working copy of /resources/... was pointing to /assessments/ in the collection.

It was screwing up both sub applications resources and assessments.

Resource was committing into /assessments, which made assessments fail and caused resources to not update.....To be more specific, it was not the entire working copy that was pointing to the wrong folder, but 2 of the 5 sub folders.

Once i saw the problem, i was able to use the tortise SVN switch command to change where my working copy was syched up to in the repository.

Lesson learned - be very careful about where the working copy is syched. This may have happened when i deleted and recreated the resources folder in the repository.

It seems now the correct way to accomplish this is to use SVN Export command. Create the directory first, then do an export from the repository and it will synch it up.