when i hit build button, line with caret at end is moved to end of above line

Hi,
Firstly sorry for my english.
I have annoying problem with resharper 8 in vs2013, its definitly caused by resharper becouse when i suspend it , problem goes away.
I dont have time to search for option which cousing this, i hope more people have same problem, so i will get fast answer here.
The problem is : when i EDIT source file and caret (cursor) is on end of the line and i hit build , debug button or F5 (which happens very often)
the line with caret is moved to end of above line. See attachments .
Thank you for helping me.



Attachment(s):
resharperproblem.png
11 comments
Comment actions Permalink

Hello Jan,

Could you please:
1. Tell which R# plugins and other VS extensions are installed for you?
2. Describe how exactly do you run the Build (shoprtcut, main menu command, toolbar button, etc.)?
3. Check if it happens on every solution (even new and just created ones), and every type of code (e.g., C#, VB.NET, Web, etc.)?

Let me know.
Thanks!

0
Comment actions Permalink

I did some further research. It happens only in one solution (but my biggest and most important) , I could not reporduce this in any other solution new or existing.
I found that this happens even in vs2010 (solution is originaly vs2010). I found that reset setting in manage settings does not help so its not caused by seting any options by myself.
I have only devexpress components and ankh svn client(tried uninstall but problem perserved) plugins installed. It happens by any action that trigger build (shortcut, button click). Solution is C# project and its winform application. This bug happens in every project in this solution.
It really annoys me :| , also when i debug i can set debug pointer becouse source file was modified....

0
Comment actions Permalink

Hello,

Thanks for the info.
Could you please try to clear caches and *.suo file as described here and check if it helps? Link is: http://resharper-support.jetbrains.com/entries/23853492-ReSharper-stopped-working-for-a-single-specific-solution

0
Comment actions Permalink

I did but nothing happens

:(
0
Comment actions Permalink

Hello Jan,

What is ReSharper version/build number you use? It is available in ReSharper | Help | About JetBrains ReSharper dialog.

Please let me know.
Thanks!

0
Comment actions Permalink

8.0.2000.2660

0
Comment actions Permalink

Hi Jan,

OK, could you please download and install the latest ReSharper 8.1 EAP build from here: http://confluence.jetbrains.com/display/ReSharper/ReSharper+8.1+EAP
After that, please try to run build on the problematic solution once again and check if it helps. If it won't, please pay attention to any exceptions which may be present (you'll note them in the bottom right corner of VS). Of any, please submit them via Exception Submitter dialog and let me know the URLs for them.

Thank you.

0
Comment actions Permalink

Didnt help :(
Also it happens only when caret is at end of the command, if i put caret to the middle of text it works normally

0
Comment actions Permalink

Hello Jan,

At this point, we're running out of the ideas... Could you please now try to 'crop' your solution to smaller sizes (e.g. remove files/references) but still with this issue present there and send it to me directly at alex[dot]berezoutsky[at]jetbrains[dot]com?

Thank you in advance!

0
Comment actions Permalink

I found what causing this behavior, but i cant tell you why(its something illegal), i can just assure you that its not problem in resharper even if it seems so (when i suspend resharper problem goes away).
Sorry for wasting your time and thank you for really good support.
JS

0
Comment actions Permalink

Hi Jan,

You're welcome.

P.S. I would much appreciate if you could contact me directly via email and describe what caused this (e.g. some library, component, 3rd party software, etc.), maybe with some abstract things without disturbing any confidentiality. It is the 1st time we encounter this behavior, and it would be good to have a solution, or at least a step forward to workaround this. I can promise that the info will not be used somehow but troubleshooting similar cases without opening your info. Thanks.

0

Please sign in to leave a comment.