External file updated after auto-complete
I have just updated to ReSharper Ultimate 2019.1.2 (Build 191.0.0.20190603.142841) and find that after every us of the ReSharper auto-complete functionality Visual Studio pops up telling me that the editor has unsaved changes but the external file has been updated. This continues regardless of whether I answer Yes or No.
I notice that if I do click Yes to reload the file from disk it does not change what is in the editor.
Is this a bug or a new feature. If the latte how can I turnit off?
Please sign in to leave a comment.
Hello Mike,
Could you please specify if the problem is reproduced in newly created solution or in some specific one?
Could you please also start VS with the following command: "devenv /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose", reproduce the issue and send us corresponding file. You can share it privately using 'Submit a request' form.
Thank you.
Thanks for the response. Some time after I posted the commentthe problem (and one or two others) went away. I have no idea what I did that might have caused it to fix itself.
For the record I was using an existing solution (~100 projects)
Sorry I can't help any more.
Hi,
I just installed ReSharper and experience the same problem. While simply typing in the editor (VS 2019), the VS-dialog keeps up popping saying the file has been changed outside the editor and if I want to reload it again. This is very annoying and unproductive. Obviously, I do not want to switch the functionality off in VS as it is indeed a handy one. So it is ReSharper that needs to communicate better to VS.
Hello Fida,
Thank you for the feedback.
Could you please specify if the problem is reproduced in newly created solution or in some specific one?
Could you please also start VS with the following command: "devenv /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose", reproduce the issue and send us corresponding file. You can share it privately using 'Submit a request' form.
Thank you.
Same thing happened to me today. Restarting VS fixed it.