Someone on SO said setup source control, it takes 5 minutes. It’s taking ages, it’s fiddly and a pain in the arse! And I don’t get the workflow
Anyway. I have svn installed on server1. Server1 is also used to store all of our existing source code and projects, which have now been added to their respective repositories on server1. We have three developers working on machines 1, 2 and 3. When we open the working copy projects on server 1 in Visual Studio (with VisualSVN), the filepath to the repos is file:///d:/foo of course when you commit you get an error message that says file:///d:/foo cannot be found because it’s on the server not the machine.
How do you make it point to file://\server/d$/foo?
I have tried
svn switch –relocate file:///d:/foo file://\server/d$/foo
Doesn’t work
The workflow part that I can’t get my head round is this. If I check out a working copy of a class project and compile it. Do I move the new dll from my working copy to production? Or do I check the dll back into source control, and then move it from source control to production? What if multiple projects use the dll, do I take it out of source control to a folder somewhere that all the projects look to, or do I copy it into the bin folders of all of the projects. Headache
EDIT:
Thank you for all of your input, I will persevere with this one!
Yes, Source Control only takes minutes to setup, however, understanding how it works is the key.
In order to answer this it’s probably best to explain how Source Control works and what you should expect to get out of it.
The book http://svnbook.red-bean.com/ (which you can read directly on line) has a fantastic explanation as to how it might work. The first couple of chapters is all you really need to glance over to get to grip with the basics.
Once you’ve got to grasp with the basics outline in the book, it should become obvious where you are going wrong with your implementation.