Expected behavior:
In VB.NET, when I start a new Private Function, Sub or Property, autocomplete displays along the way. For example, Typing "pri" will display "Private" and "fun" AFTER Private shows "Function".
Observed behavior with CodeRush enabled:
Typing "Private" and a space and then "fun", Intellisense does not show anything.
Disabling CodeRush and restarting VS 2019 reverts Intellisense back to the prior, expected behavior.
This just started in the last release of CodeRush.
To reproduce the issue, in VS 2019:
- Create a new VB.NET Console app using the .NET Framework.
- Open Module1 if not already open.
With CodeRush Disabled:
-
After the 'Sub Main' block and before 'End Module' we'll create a new Function.
a. Type "fun" and Intellisense shows "Function". -
Delete the previous Function code.
-
Now we'll create a Private Function.
a. In the same spot type, "pri" and Intellisense shows "Private", tab and space to accept.
b. On the same line, type "fun" and Intellisense shows "Function".
With CodeRush Enabled:
-
After the 'Sub Main' block and before 'End Module' we'll create a new Function.
a. Type "fun" and Intellisense shows "Function". -
Delete the previous Function code.
-
Now we'll create a Private Function.
a. In the same spot type, "pri" and Intellisense shows "Private", tab and space to accept.
b. On the same line, type "fun" and there is no Intellisense.
This is very frustrating as this behavior is slowing down my coding.
I just checked and this issue does not occur in VS 2017. It only occurs in VS 2019.
Hi William,
Thank you for letting us know about the issue. I replicated this behavior and need additional time to discuss it with our R&D team. We will notify you once we have any news.
In the meantime, as a workaround, I suggest you disable the Naming Assistant feature on the CodeRush > Options > Editor > Visual Basic > Naming Assistant option page:
Your VS 2019 workaround does work on my end. I do hope this is only temporary; the naming assistant is a time-saving feature.
FYI. I looked in VS 2017 and the Naming Assistant is enabled there. VS 2017 has no issues with the Naming Assistant.
Thank you for the confirmation, William.
I can confirm that. It is because Visual Studio 2019 has its own completion mechanism, so the issue is reproducible only in Visual Studio 2019 and later.
I'm afraid I can't provide you with any estimates at the moment. We will update this thread once we have any news.