Namespace Conflict

[iain.waddell]

We've made some big changes to our code base, requiring many classes to be deleted. For some reason Vault is showing Namespace Conflict next to all the deletes.

If I right click and choose resolve nothing happens. The only way I've found to resolve the issue is to undo the delete and delete the file again and quickly submit the change before Namespace Conflict reoccurs.

Can anyone explain how a Namespace Conflict can occur for a delete?
And what I can do to stop in happening?

I'm using Vault Standard 5.1.2.

Iain

[Beth]

Are you performing the delete from inside the Vault GUI client or from inside a connected IDE such as Visual Studio?

Can you post a screenshot of the error?

[iain.waddell]

I work inside VS2008 but actually commit using the Vault Client.

I knew I should have taken a screenshot when I posted. Just checked now and it's all correct. I'll post a screenshot when it all goes wrong again.

Iain

[iain.waddell]

It's gone wrong this morning.

Screenshot attached.

Iain

[iain.waddell]

Just restarted the Vault GUI and its reset the namespace conflict except for one file which is in the list twice (for some reason), once as a delete and once as a namespace conflict.

Screenshot attached.

Iain

[Beth]

Namespace conflicts normally occur when there are two items in the same space with the same name. If you have have a rename to a file that needs to be deleted first this can happen.

Try committing a delete first and then if you have renames or adds to apply, then apply those.

[iain.waddell]

I ended up removing both items and deleting the entry again. This time it worked.

Iain

[iain.waddell]

Do you have any explanation for all the "Deleted File" entries turning into "Namespace Conflict"?

Iain

[Beth]

It's possible that something got in the way of the Vault cache getting it's updated information, and that by reopening Vault you restored the connection it needed. A refresh might have been enough a well. It's hard to say after the fact.

[iain.waddell]

I've been having this problem for months. Refreshing never seems to work. Sometimes restarting the client isn't enough.

On occasions when I can't get it to sort itself out I have to undo the delete and then delete them all over again.

Iain

[Beth]

Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? We should look into this further since you are having a recurring issue with this.

If there's any kind of network glitch going on, that could contribute to the issue. Those can be hard to track down sometimes.

HS: 228254

[bbrewder]

I have the same problem. I've deleted a number of files in my project (in VS) and they all have "Namespace Conflict" in the "Folder" column in the Vault Pending Changes window (all the column names are wrong in this window as well, I don't know why). I can't be sure, but I think the "Namespace Conflict" showed up after I checked in a file in the solution. Closing VS and the Vault client didn't clear it up, nor did clicking File -> Vault Source Control -> Refresh Source Control Status.

I did attempt to commit a delete in the Vault client and it succeeded. I'm not ready to commit my changes in VS yet, but it would be nice to get this issue resolved so I don't have to worry about it.

[Beth]

Do you have any adds in your pending changes window as well?

In Visual Studio go to File - Vault Source Control - Change Bindings and look at the paths that the parts of the project are bound to. What do you have set there?

Then look at the working folder settings in Vault. The bindings in VS need to match how you have your working folders set in Vault.

After checking the bindings, go to %temp% and find the file VaultGUIclient.txt. Are any recent errors showing in that file?