2 things we can't figure out

[Don Robinson]

We have just moved 2 repositories from VSS - all went well, but there are 2 issues to ask about:

1//
We linked the Vault repository to a VB project file. After some fiddling, it works; mostly.

First open the Vault Client and the VB Projet file at the same time. When you check out a given module in the VB project, then switch to the Vault client and refresh, the corresponding file will show as checked out. Check it in on the VB project, etc., and it shows checked in. Good: they are synchronized.

But... check it out on the Vault client side and it will not show as checked out on the VB project even after you choose Tools | SourceGear Vault | Refresh File Status. (The icon appear changes, however, so that the lock symbol disappears.) To find the current status correctly, you need to actually re-open the VB project. Not Good.

Is there some configuration issue here?

2//
When you do multiple checkouts using a mixture of binary and text-type files (e.g. *.frx and *.frm), the entire checkout reverts to 'Exclusive' (appropriate for binary), rather than a mix of Exclusive and non-Exclusive. Is this a design feature or a glitch?

[dan]

But... check it out on the Vault client side and it will not show as checked out on the VB project even after you choose Tools | SourceGear Vault | Refresh File Status. (The icon appear changes, however, so that the lock symbol disappears.) To find the current status correctly, you need to actually re-open the VB project. Not Good.

We don't currently have refresh hooked up in the IDEs, because the VS API doesn't distiguish between a user invoked refresh and VS-invoked refresh, and VS called this function almost continuously, which killed performance.

We are considering ways around this so that this menu option will work. In the meantime, try a Get operation, which does do a refresh, or if you want something that doesn't change anything, invoke Vault Properties on a file, and this should refresh as well.

2//
When you do multiple checkouts using a mixture of binary and text-type files (e.g. *.frx and *.frm), the entire checkout reverts to 'Exclusive' (appropriate for binary), rather than a mix of Exclusive and non-Exclusive. Is this a design feature or a glitch?

Yes, this was intentional, in that we decided that when it is ambigous which mode to use, it is "safer" to just the check files out exclusively. Also, it would have been misleading to allow the user to specify non-exclusive checkouts, but then check out the binary files exclusively anyway, which would likely generate unwanted tech support calls