Bug 7682 - SourceGear Vault interaction?

As I noted in my comment to the tracker for bug 7682 (which has managed to persist since build 201), this appears to be some sort of interaction issue between Vault and ReShaper.

Does this make it too specific of an issue to deal with? (I realize there are a few thousand other bug( report)s to deal with as well...

Oskar Austegard

7 comments
Comment actions Permalink

Hello Oskar,

I've taken a look at that request. Could you please clarify some points.
First, do I understand correctly that the problem occurs when the user does
a check-in into Vault? Second, what are the consequences of the problem except
for appearance of the exception reporting form? Third, does Vault install
some kind
of extension into VS.NET?

Thank you in advance.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

As I noted in my comment to the tracker for bug 7682 (which has
managed to persist since build 201), this appears to be some sort of
interaction issue between Vault and ReShaper.

Does this make it too specific of an issue to deal with? (I realize
there are a few thousand other bug( report)s to deal with as well...

Oskar Austegard



0
Comment actions Permalink

Dmitry, thanks.

For me at least, the bug only happens when attempting to modify a file that is not yet checked out, causing a check-out - my suspicion is that ReSharper is not able to wait for the check-out to take place.

I deliberately tryed to lock down what causes the error:
1. Opened a file, currently checked in to Vault.
2. Attempted a Refactor - Rename.
3. When ReSharper attempts to modify the file, the check-out file dialog appears. Immediately thereafter (or in parallel) the ReSharper error dialog appears.
4. The rename operation fails - the original variable is renamed, but not the other usages of the variable.

There are no add-ins to VS by Vault that I know of, other than that Vault is "registered" (for lack of a better word) with VS as the source-code provider.

I have posted a message to the Sourcegear Vault forum to see if someone from Sourcegear can shed some light on the issue.

0
Comment actions Permalink

Hello Oskar,

thanks for your help! Actually, I've been able to reproduce this exception
without Vault with VS2003. It seems to has something to do with appearance
of modal forms (and there are internal reasons confirming this hypothesis).
The problem
is fixed in 209 which we plan to release in 2 days.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Sourcegear forum link:
http://support.sourcegear.com/viewtopic.php?p=19452



0
Comment actions Permalink

Great! I deleted the Sourcegear forum posting.

0
Comment actions Permalink

Thanks for the attempted fix - unfortunately it did not work... Did the same test in build 209 and got the same result.

0
Comment actions Permalink

Hello Oskar,

ok, I've already realized that the problem is more general... We're looking
into it. Perhaps
I'll need to play with Vault to figure it out.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Thanks for the attempted fix - unfortunately it did not work... Did
the same test in build 209 and got the same result.



0

Please sign in to leave a comment.