autocomplete is not working but intellisense working fine (VS 2019) resharper version: 2019-3-1 Follow
After I upgraded my framework from 4.6.1 to 4.7.2 in my solution, resharper autocomplete stopped working. It still has the intellisense tho. Lets say I am trying to enter "[HttpGet]" and when I type "[Htt" it shows me the http verbs like below:
but when enter or click on it to autocomplete, it just replaces the whole text with underscore and space so it looks like "_ " like this like below:
HttpGet is just example, whole solution is like this now. I need help! Tried so many things i found on web, cleared all the cache folders, updated resharper, cleaned user temp folders etc.. but none of them worked. If I switch to use Visual Studio for intellisense, it works, but when I switch back to Resharper, it does not.
Please sign in to leave a comment.
thank you for the feedback.
Could you please try disabling ReSharper | Options | Environment | General | Read solution model directly and check if it helps?
Yes, disabling the resharper or even just switching the visual studio intellisense fixes the issue. As soon as I use resharper it happens again. Just to mention again:
Restarted Visual Studio
Cleared solution cache folders
Personal Cache folders
None of those worked.
Hello Brandon B.,
I meant disabling "Read solution model directly" option located in ReSharper | Options | Environment | General.
Could you please try disabling it and check if it helps?
I tried disabling "Read solution model directly" but it didnt work.. It works with other solutions. I dont why specifically with this solution it started not working.. Can you please help!
Could you please run Visual Studio with the following command line: 'devenv /ReSharper.LogFile c:\log\resharper.log /ReSharper.LogLevel Verbose', reproduce the issue and send us a corresponding 'resharper.log' file. You can share it privately via "Submit a request" form at the top of the page.
Angelina Elycheva - I sent the logs almost 10 days ago but what happened??? I havent heard any update.
As far as I see from the request you've submitted that there was a private build suggested and it seemed to fix the problem.
I'd like to let you know that the fix of the problem will be included in the upcoming ReSharper 2019.3.2 what is going to be released shortly.