Serious Vault issues re. Shared and VS2015 plugin

[KasparJejo]

We are using Vault 9.1 Standard together with VS.NET 2015. I have SERIOUS issues with the plugin and several questions on the "Share" function.

1. The plugin (2015) seems to randomly not detect file changes, resulting in the dreaded "renegade" status. Especially project files - which get altered when adding files and/or references. (seems the plugin does not pickup on these actions). However, in the solution explorer, all files have the closed padlock icon, and "appear" to be checked in. This is a MAJOR issue because the actual version in Vault itself is outdated and missing several files until manual intervention is done. We are now inclined on moving away from Vault altogether since these issues create a non-workable environment. (The VS2008 plugin DOES work 100% and had loads of extra features. What happened?)

2. The Share feature in Vault. We assume this works the same way as "Externals" in SVN. We use this feat to create links in order to have projects reference other projects.
o Why are these files being flagged as "Needs Merge" in locations other than the original folder ?
o Why are these files being flagged as "Renegade" - same.
=> Shouldn't these files ALWAYS follow the originals, regardless ? I would be happy to get some details because I must be doing something wrong here

3. I get messages telling me files are "duplicate" despite the fact they do not show in the Vault client. Seems it is fairly easy to mess up, blocking check-ins. (recursive check-out/check-in also fails and manual file-by-file check-out/in is needed. Our time is precious)

I am sure we're doing something wrong here. Apart from the plugin - pretty sure that just does not work properly.

(We are a paying customer going by the name of SWYLYX (BE))

[Beth]

Can you post a screenshot of the settings in the Vault Tools - Options - Concurrent Development Style?

In your VS 2015 solutions, do you use the Vault Classic Client or the Vault Enhanced Client? That setting is in the VS Tools - Options - Source Control - plugins.

[KasparJejo]

Hi Beth. Sorry for not getting back to you sooner. Things were quite hectic here past months. In the meantime, we migrated to VS.NET 2017 now using the VS.NET 2017 extension. A BIG DIFFERENCE! A lot of renegade issues are now resolved as well as the funky stuff going on with the shares. So that's good.

The only issues we have - and may be just features of bugfixes - are:

- packages.config changes are not always detected (nuget)
- multiple file operations on the same file (i.e. rename, delete, ...) without intermediate check-ins sometimes cause failure (most likely because the order of operations ?)
- For customer support and development, we often work with VPN connections causing local network and routing changes. The plugin keeps timing out each time a key is pressed when the server cannot be reached. Would be fab to have the plugin be a bit smarter about this and (offer to) switch to offline mode automatically.

Other than that, all quiet on the Western front!

[joe_sg]

Hello there! Thank you for reporting these issues with the new VS 2017 extension.
Beth is no longer with Sourcegear, having moved to St Louis. I have logged 2 bugs and a Feature Request and will reproduce them and go over them with our developers. (19970, -71, -72)
I'm glad things are otherwise going well.
Thanks again for contacting Sourcegear Support.

[joe_sg]

Re: the packages.config, nuget issue, a developer offered these comments:

Is it safe to say you're using the Concurrent Development Style options of 'Require Check Out before Check In' and 'Make all files read-only'? If so, can you try to run 'update-package' from the Package Manager Console, does it check out the packages.config file?

Another option is to change your Development Style, that way when Nuget writes directly to package.config or your solution or project (and bypasses the source control events from within Visual Studio), Vault will automatically pick up the changes.

I hope this helps.

[BrianDrab]

Are these bugs fixed yet? We are encountering the same thing. Nuget packages that are modifying the files outside of vault so they become renegade.

I was trying to understand the last post...is that a potential workaround? Are you saying to change the "Concurrent Development Style" in vault? If so what do we change it to?

Please let me know. Thanks.

[Tonya]

Hello,

The bugs in regards to this issue have not yet been addressed yet. The workaround suggests to change your Concurrent Development Style from VSS to CVS mode.

Thanks,

Tonya

[BrianDrab]

We tried the workaround of changing the Concurrent Development Style from VSS to CVS mode and it doesn't work. Same issue. Anything else we can try?

[Tonya]

I wanted to let you know that we are currently looking into this. I will update the thread as soon as we have more information to share.

Thanks,

Tonya

[BrianDrab]

OK, thanks. If you need to jump on one of our machines and have us walk you through the issue please let me know. We can do this.

[Tonya]

Brian,

We have discovered that changing the development style alone is not sufficient. The 'read-only' flags also need to be removed from files in the working folders. Performing a GET after switching modes should remove the read-only flags.

Please let me know if this doesn't help.

Thanks,

Tonya

[BrianDrab]

OK, thanks. Not ideal but it does work. Two final questions.

1. Any ETA on these bug fixes?
2. Is Vault a product that you going to be sun-setting?

[Tonya]

Brian,

I don't have a time frame available for the fix but we are currently working on Vault 11 and most bugs/feature requests will be considered.

Vault is a continued supported product and our plans are to release Vault 11 sometime this year. Keep an eye out for updates available on our website.

Thanks,

Tonya

[BrianDrab]

Awesome, thanks!