SourceGear Support

You can pin them and I think you can lock the share itself down using folder permissions (have you tried this?), so there are some options from my point of view. Also, I think that the current behavior is ideal because it does exactly what it is told to do: stuff underneath folder a cannot be change...

Just for the record, this used to work just perfectly with V3.x when Dragnet was still supported - I did build up a Dragnet mock page using ASP.NET which took very little effort to be done, but this stopped working when V4 dropped Dragnet support. Having a generic plug-in concept on the Vault server...

Actually, the behavior you're describing is better than what I expected. In fact, I believe that this is the ideal behavior.

Well, you do see the file as shared in the Windows GUI client. I'm not sure what happens if you use folder permissions to try to achieve what you want, it may work...

To reproduce, start Eclipse and open a Project which is bound to Vault, log in. Everything is fine so far. Now recycle the application pool of your Vault server. This will obviously invalidate the session token used by the Eclipse client. In the still open Eclipse, try to edit a checked-in file. It ...

There is a connection string in the appSettings section of the web.config file.

Note: I'm not a Sourcegear staff

You can pin a share to a specific version, which in fact makes it read-only and the version will not change when doing a get latest of that share unless you change the pin. I guess this may help you.

Note: I'm not a Sourcegear staff

This never happened in V4.1.2 before. But today I was still able to use all the server settings just fine, and I was also able to change the default repository settings as well as opening the main page for a specific repository, but as soon as I tried to change any setting of the repository, the pag...

We had some server trouble in the last days and the Vault application pool has been recycled several times. The Windows GUI client and the MSSCCI and VSIP clients have no trouble to reconnect in this situation. However, the Eclipse client seems unable to deal with this, and I had to re-start Eclipse...

lbauer wrote:What version of Vault are you using -- Server and Client?

Both the newest available (4.1.2.18185).

When selecting both a non-ghosted file and a ghosted file in the UI and right-clicking on those, no popup menu is shown and all menu entries disappear from all menus. (However, the menus will come back after the file selection is changed.) I would have expected to see the option to compare the two s...

I've reproduced this and logged a bug. Great, looking forward to the fixed version! We made some intentional strides in this area in 4.0, but obviously it's not yet 100%. This bugs me personally, so I'm motivated to get it on a schedule, but it's not yet on one. Sorry to bug you more, I've just got...

This is strange, because the client does almost exactly what you describe (sort change set items before sending them to the server), for the reasons you give. Is it sorted by change type or is it sorted by a sequence/date? What client are you using to perform this commit? What version? This specifi...

In the feature description of Vault, it states that all operations are atomic so that the repository is not left in a half-baked state. That's nice. Now the problem I'm facing every now and then is that commiting all pending changes will just not work, especially when items are moved, renamed, and a...

It does not mean to use an existing working folder assignment to determine where on disk to stick the source. Which is unfortunately what people intuitively expect it to mean. Note that this is how the old plugin works, too. Ian, how does this have anything to do with the issue reported? I don't se...