Using multiple machines for work - checkout not right

djMax · Post by **djMax** » Tue Jun 01, 2004 8:33 am

I use multiple machines (desktop at work and laptop at home) to do development. It seems that Vault cannot associate checkouts with anything more than the username, because if I check out on machine A, it shows it as checked out on machine B, as opposed to "exclusively locked by someone else" which is what I would think it should do. Am I missing something here?

lbauer · Post by **lbauer** » Tue Jun 01, 2004 8:58 am

If you checkout a file from Machine A, Vault won't let you check it in from Machine B.

You can, however, check files out from more than one machine.

To prevent that, check the file(s) out exclusively, and you won't be able to check them out again on another machine.

djMax · Post by **djMax** » Tue Jun 01, 2004 11:22 am

My problem is slightly more complicated, which is that I don't want the file to APPEAR checked out on machine B, since as you say I cannot edit/checkin that file on machine B. But as of now if I checkout on machine A, it shows up as checked out on the vault client or visual studio IDE on machine B.

lbauer · Post by **lbauer** » Wed Jun 02, 2004 7:14 pm

Vault, like most source code control systems, tracks what happens to files during the development process. Checkouts, modifications, checkins, etc. are there for all users to see -- including yourself.

Is there a particular reason you don't want the file to appear checked out? Is it a problem for your own files that are checked out or would you not want to see any user's checked out files?

djMax · Post by **djMax** » Fri Jul 02, 2004 2:59 pm

interesting. maybe this is enough. It was my impression that this would confuse visual studio, but if it doesn't then it makes some sense... Technically I think it should show the "not check-outable" icon (the little blue circle with the slash) rather than the "checked out by you" icon, but if the functionality is the same then fine.

djMax · Post by **djMax** » Wed Jul 07, 2004 9:03 am

So I don't think this works as it should.

*) Have same project on machine A and B
*) Checkout file on machine A
*) Open project on machine B
*) File shows checked out on machine B
*) File is editable on machine B

There is no way that file should be editable on machine B.