Search found 5 matches

by mcutter
Tue Mar 09, 2010 2:21 pm
Forum: Support (Vault)
Topic: VS2010 null reference errors
Replies: 3
Views: 1564

Re: VS2010 null reference errors

Project has already been upgraded from VS2008 to VS2010, using Vault Enhanced Client for both. This happened several more times and then I discovered that all of the projects had gone offline. So I restarted VS2010 and they are all back online. Other developers are connected to the same repository a...
by mcutter
Tue Mar 09, 2010 11:22 am
Forum: Support (Vault)
Topic: VS2010 null reference errors
Replies: 3
Views: 1564

VS2010 null reference errors

We upgraded to Vault 5 and VS2010 last week.
Twice today I have been unable to check in changes from VS2010, with a null reference exception.
The workaround each time was to check in with the Vault Client, which is slightly inconvenient.
by mcutter
Mon Sep 14, 2009 9:47 am
Forum: Support (Vault)
Topic: How to roll back to a label/date?
Replies: 50
Views: 52363

Re: How to roll back to a label/date?

I also want to cast my vote for the ability to rollback to a label. I just had two dozen changes to rollback and was shocked to find that there was no automatic way to do this. The recommended solution of checking out the labeled version to a different folder, then checking the entire project out, c...
by mcutter
Wed Nov 05, 2008 3:00 pm
Forum: Support (Fortress)
Topic: Error 1722 during Fortress Installation
Replies: 14
Views: 13096

Re: Error 1722 during Fortress Installation

I similarly got the error when trying to open a dbp
Error: The parameter is incorrect.
File: vsee\lib\xfcstr\winstrw.cpp

Turns out that the vs2008 source control plug-in had somehow gotten set to classic client.
Changing back to enhanced client allowed me to open the dbp without any problems.
by mcutter
Wed Oct 22, 2008 8:50 am
Forum: Support (Vault)
Topic: 4.1.1 - Several Vault folders to the same physical one?
Replies: 11
Views: 5214

Re: 4.1.1 - Several Vault folders to the same physical one?

I find this restriction to be annoying and would like to propose that it is trivial to use namespaces for the state folder to avoid conflicts. One should be able to set working folders without having to nest folders. Please reconsider fixing this feature!