R# Source Control, Debug intellisense
I've been a long time beta tester of R# and a fan of the product. I stepped away from the 2.0 EAP because of stability problems that I didn't have time to deal with.
I'm having some issues with the beta. First, I get extremely bad behaviour when automatically checking out a file. I use source gear, and ever since installing the beta, VS.NET 2005 pro often hangs when I try to check out a file by simply strating to edit it.
I also noticed that R# intellisense doesn't work in the watch window. Either make it work, or don't disable VS.NET's for that area.
Overall I find that the intellisense doesn't kick in as much as it did in 1.0. Turning it on for "every character" causes serious performance issues. Ctlr-space...I know I know, but I'm sure it's not coming up when it should by itself.
Karl
ASP.NET MVP
Please sign in to leave a comment.
Hello karl,
1) How long do those hangs you experience when checking out files last? Or
are they real hangs? In that
case it would be great if you attach the debugger to the hung devenv.exe
and capture stack traces which you may post here.
2) Concerning IntelliSense in the Watch window, it's unfortunately not as
easy as it may seem. ReSharper programmatically disables VS IntelliSense
after typing dot to avoid displaying two IntelliSense windows
in the editor (ReSharper's one and VS's one), but doing so also disables
it in the Watch window, since VS IntelliSense in all places is controlled
by the same option. It is thus not possible to disable VS's IntelliSense
for editor only. Nevertheless we're going to address this problem in a near
future. The workaround is to use
Ctrl-Space to make VS IntelliSense show manually.
3) Could you please clarify what do you mean by 'intellisense doesn't kick
in as much as it did in 1.0'? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
I too get this issue with Source Control operations, I too am using Vault (Sourcegear), and find that if I check-out a file by starting to code I get my VS using 100% cpu for 30-40 seconds, until it then goes back to normal, if I then try to undo-check-out, the context menu doesn't appear for ages, again 30-40 seconds.
In fact, right clicking on any of the files to perform any operation gives this sort of time usage.
Attaching the debugger to devenv doesn't appear to give any stack trace information that I can see. (Though it is 100% possible that I've attached it incorrectly, I've not had much call to debug external apps!!)
I should add, that a second right-click after the first responds normally:
1. Right-click - 30-40 second wait
2. Right-click - no wait,
3. Select undo-checkout - no wait
4. Right-click on same / different file - 30-40 second wait
5. Right-click - no wait
... etc.
Chris
Hello Chris,
what exactly do you mean under 'a second right click'? Second in a particular
file or second altogether? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Second alltogether in this case.
Hello Chris,
that's odd. So do I understand correctly that half of right clicks proceed
normally, while the other half are slow?
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
I should really stop posting messages straight away:
The second click on the same file will be instant.
The second click on a different file will produce a noticeable delay of maybe 2-300ms, but certainly manageable.
Hello Chris,
well, this may be related to caching results of file parsing. If that is
true, then changing all the text of a file (by Cut and Paste all the contents)
should also cause slowdown.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hi Dmitry,
From scratch :)
Assume project has 2 files, FileA & FileB.
1. Right click on FileA, - Wait 30-40 seconds
2. Right click on FileA - instant
3. Right click on FileB - small time lag, maybe closer to 50-100ms, it's noticeable, but to be honest I'm not very good at estimating ms :)
4. Right click on FileA - small time lag,
5. Right click on FileA - instant
6. Actually do Undo-Checkout
7. GOTO 1.
Chris
Cutting and pasting entire file contents does give a minor lag as with the right-clicking, but as I said that's manageable and usable!
Hello Chris,
ok, I see. Could you please try if the problem is repeatable on a solution
not under source control (ideally, on the same solution
with source control temporarily disabled)? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Sorry for not following up. I too have failed getting any meaningful debug information. I have found a workaround though, disable CodeRush.
I make sure to go into the Add-In manager and disable "DevExpress Tools" and there is absolutely no hang up.
Chris, do you have DevExpress installed too?
Is CodeRush an addin as well?
I don't have CodeRush or DevExpress tools...
The current addins I'm running are:
SmartPaster
CodeKeep
I'll have a go at disabling them and see how it goes.
Hello Chris,
yes, CodeRush is an add-in produced by the Developer Express firm.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hi Dmitry
With source control unbound on the same solution the problem does go away.
i.e. I can right-click on any file, with no delays visible at all.
When I say 'no delays' there is still the massive delay when I first open the solution, and first click on the Solution explorer, but once that has resolved itself it works ok.
Chris
Message was edited by:
Chris Skardon
Hello Chris,
so how about disabling other installed add-ins? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Disabling the Addins had no effect whatsoever :(
To summarize : ReSharper causes slowdown if source control is enabled, right?
Does it depend on file size?
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Yep,
Specifically in this case 'SourceGear - Vault' (http://www.sourcegear.com/).
sorry, filesize doesn't appear to be an issue.
My solution is fairly large though (139 projects).
Chris
Message was edited by:
Chris Skardon
For me "slowdowns" is a generous term...it crashes devenv.exe
It does seem related to source control (i haven't tried anyting other than vault), it doesn't seem related to file size whatsoever. As I've said, disabling CodeRush fixes the problem.
It doesn't 'crash' my environment, but definately makes it unusable until it's finished it's cpu intensive jobby.