Resharper does not wait long enough for file checkouts

We have the misfortune to be using CrapCase (Rational ClearCase) at my current workplace and as most people know it is horribly slow. Where this causes a problem is that Resharper always cancels the action it was performing when trying to checkout a file as it must have a very small timeout.

If I open a class file and see a warning I want to resolve (such as removing an unnecessary variable initialisation), then hitting Alt-Enter, Enter starts the checkout as desired, however Resharper does not apply the change.

So then I repeat the Alt-Enter action - however if I do this too quickly then Resharper has not reparsed the file, and instead the top menu item is always a "Suppress warning xxx by #pragma" which obviously was not my intent. So then I have to ctrl+z and try again (or just wait longer for Resharper to catch up).

I get a similar issue with renamings - if it requires file checkouts the whole operation gets cancelled the first time, then I hit shift-F6 again, type me new name again and it succeeds...

Regards,
Grant.

7 comments
Comment actions Permalink

Hello Grant,

do I understand you correctly that whatever ReSharper's operation requires
checkout of a file, it
always cancels right after (successful) checkout and you have to redo it?

Concerning the timeout - ReSharper itself doesn't set any
timeouts, nor does it know about ClearCase directly - all it does is asking
VS to make a specific file editable.
If a file is under ClearCase version control, this likely involve communication
with a server and other related activities.

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


We have the misfortune to be using CrapCase (Rational ClearCase) at my
current workplace and as most people know it is horribly slow. Where
this causes a problem is that Resharper always cancels the action it
was performing when trying to checkout a file as it must have a very
small timeout.

If I open a class file and see a warning I want to resolve (such as
removing an unnecessary variable initialisation), then hitting
Alt-Enter, Enter starts the checkout as desired, however Resharper
does not apply the change.

So then I repeat the Alt-Enter action - however if I do this too
quickly then Resharper has not reparsed the file, and instead the top
menu item is always a "Suppress warning xxx by #pragma" which
obviously was not my intent. So then I have to ctrl+z and try again
(or just wait longer for Resharper to catch up).

I get a similar issue with renamings - if it requires file checkouts
the whole operation gets cancelled the first time, then I hit shift-F6
again, type me new name again and it succeeds...

Regards,
Grant.



0
Comment actions Permalink

Dmitry,

19 times out of 20 your statement is indeed what I meant - Resharper cancels it's operation because the checkout has not completed "quickly enough". About 1 time out of 20 the checkout is quick enough and the Resharper action is able to be applied.

Obviously it gets pretty annoying after a while, particularly when going through a mass code cleanup. I have to train myself to checkout the file first (which doesn't really work with multi-file refactorings unless you know all the usages up front).

As an off-topic aside - when reading the desired feature list for 3.0 a while ago I believe you guys listed a feature allowing visibility of Resharper warnings across projects/solutions, rather than requiring opening each class file in turn. Is this still in the plans?

Regards,
Grant.

0
Comment actions Permalink

Sorry I'm still missing - why do you think that the operation cancels because
it cannot complete "quckly enough"? Is there any message
about timeout or something like it?

Thanks.


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


Dmitry,

19 times out of 20 your statement is indeed what I meant - Resharper
cancels it's operation because the checkout has not completed "quickly
enough". About 1 time out of 20 the checkout is quick enough and the
Resharper action is able to be applied.



0
Comment actions Permalink

We're using StarTeam, and sometimes have to wait as much as 30-60 seconds
for a file to be checked out. I can't remember experiencing the problems you
describe. We have silent checkout enabled, and when I hit Alt+Enter Enter on
a R# suggestion, the code is checked out and changes made to the file as
soon as the file is writable.

I'm using 3.0.2 build 500.

Regards,

Dag


0
Comment actions Permalink

Dag - I wish my experiences were always the same as yourself (not the delays, but Resharper doing the job when the file is "ready"). That is exactly the behaviour I would like/expect. No wonder Dmitry is confused if he is fortunate to get the same "things working as they should" result.

Dmitry - there is no message of any timeouts or such like. The Resharper operation just fails, even though the file is now checked out. What I do get is a tooltip that says "Failed to modify documents". I can also see the lightbulb change to having a cross in it as it reparses and eventually comes back to the original icon - thats the bit I was talking about which the delay in doing this causes me to Alt-Enter/Enter on the wrong "action" if I am too quick before that reparse takes place.

We do work with "larger" solutions (45 projects, thousands of classes) so not sure if that is a factor at all. This is completely repeatable behaviour for us - but not something I remember taking place before the 2.5 versions. I am using 3.0.504.27 currently

Regards,
Grant.



Attachment(s):
FailedToModify.png
0
Comment actions Permalink

Just my two cents worth. When using ClearCase I get the same behaviour as Grant, especially when ClearCase is slow about checking out files.

Grant, I feel your pain. Our new project is under subversion, so no more ClearCase :) :) :)

0
Comment actions Permalink


"James Hebben" <no_reply@jetbrains.com> schrieb im Newsbeitrag
news:31027657.1185783805897.JavaMail.itn@is.intellij.net...

Just my two cents worth. When using ClearCase I get the same behaviour as
Grant, especially when ClearCase is slow about checking out files.


I've read in a german forum that there are some issues with ClearCase an
Visual Studio. The issues was not specified in that post, it was an flame
post about Visual Studio. So it maybe ClearCase problem.

--
Regards

Albert Weinert
MVP Visual Developer ASP.NET

http://der-albert.com

0

Please sign in to leave a comment.