SourceGear Support

Does SourceGear log actions such as Undo Checkout on files done from the Admin console? If not, this would be a helpful feature.

Thanks for your input GregM. ThomasC: We do try to put in features that will make as many customers as possible happy and keep Vault stable. Sometimes that conflicts with what other users want or have as a priority. We don't have anything against this particular feature. I will let the developers k...

However, if we are talking about SourceSafe users, they never had the ability to do anything other than exclusive checkouts. That is incorrect. The first option on the first page of the SourceSafe admin tool options dialog is "Allow multiple checkouts". The Vault setting exactly matches t...

Look, I fully understand the whole idea of prioritizing features. However, if we are talking about SourceSafe users, they never had the ability to do anything other than exclusive checkouts. By allowing the client to not checkin exclusively, you are by definition adding a new feature. SourceGear the...

In the past 12 years, have most of your developers been ex-SourceSafe users in remote locations with egos the size of football fields? If I were working with ex-CVS developers who were transitioning to Vault, I can see how such a feature would be unnecessary. The difference between this feature and ...

It has been a couple of years since I posted this: http://support.sourcegear.com/viewtopic.php?f=5&t=7938&start=0&st=0&sk=t&sd=a And I still cannot deny exclusive checkouts. I really do not understand the resistance to this feature. You allow for requiring exclusive checkouts on ...

I have mentioned this before and it has fallen on deaf ears. You really, really, really need to make an option on the server that prevents users from exclusively checking out mergeable files. Out of the box, VS and Vault will enable exclusive checkouts even with the enhanced client. This is a seriou...

We just upgraded from Vault 3.5 to Vault 4.1 and we are using Nant .85.

I'm going to guess, given other nant timings that the culprit is vaultsetworkingfolder. So, the question is why would that be so slow?

I second that working with the nant tasks is a bear. This is primarily due to the documentation. For example, the vaultlistchangeset docs states: "Returns the collection of change set items that are pending." The Sphinx (Mystery Men) would be proud of that sort of redundancy. What exactly ...

Some months ago when Vault 4.0 was first released I asked whether it would be possible to prevent users from checking out mergeable files exclusively. As I read the most current documentation on Vault 4.1, it still does not appear that this restriction has been created. Am I correct in stating that ...

I'd love to but the problem is that I have developers with a range of experience in separate locations and they can be difficult to control. ;-> The real bugger is project files. I can somewhat live with exclusive checkouts on individual cs and markup files but allowing developers to exclusively che...

Given what you have said, then I would phrase the requested feature as providing the ability to deny exclusive checkouts on mergeable files. In other words, force users to merge mergeable files.

Let me add one more thought, does it not seem obvious that if you are going to provide a feature that lets Admins restrict users to one style of checkout (Require exclusive checkouts) that it makes sense to have a feature that let's Admins restrict users to the other style checkout?

Correct me if I'm wrong, but the default API in Visual Studio is the old MSSCCI API. The developer has to consciously change the configuration in their instance of Vault in order to enable Edit-Merge-Commit style checkouts. Is that not correct? If my goal is to move developers off of exclusive check...