VB .net Dim Statements
Normally, VS changes "dim" to become "Dim" but with ReSharper it is leaving it as "dim" - which is not what I want - it doesn't conform to current standards.
I read about Live Templates, and there is one for Dim statements. So I turned that off and restarted VS and all was well for a little while. However a few minutes later the problem returned. I checked the IntelliSense Completion Behaviour option for Replace keywords with Live Templates and it was still set OFF, just as I had left it, and yet "dim" is still remaining in lower case.
If I type "dim something as string" without ReSharper then VS normally changes it to "Dim something as String" which is what I want to happen.
I can't tell whether ReSharper is causing this directly or whether it is simply slowing down IntelliSense so that it can't keep up with me any more. For example: if I pause having typed "string" before pressing Enter then it will offer me "String" and will change it to that when I press Enter although the "dim" keyword still remains in lower case.
I'm running on Dell XPS 8930...
Processor Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.8 GB
Available Physical Memory 4.66 GB
Total Virtual Memory 31.3 GB
Available Virtual Memory 12.4 GB
Page File Space 15.5 GB
VS Community 2017 V15.9.23
ReSharper Ultimate 2020.1.2 built 2020-05-06
Any suggestions?
Please sign in to leave a comment.
This is not only the case for "Dim" but also other keywords (like If, Then etc.)
Thanks for the reply. That was very useful to me as there was a slim possibility that it might have been due to a slowing down of VS possibly caused by ReSharper (others have reported that as an issue, although so far I haven't noticed anything along those lines); so your response kind of confirms that this is a "feature" albeit for me an undesirable one.
I did notice that if you select a block of code that has these undesirable case changes and Ctrl-K/F to Format it then the capitalisation returns to normal. But it's a pain to have to keep remembering to do that.
Do you know if this "feature" can successfully be turned OFF or otherwise nobbled? I'm only a few days into my 30-day trial of ReSharper so I am not qualified to pass judgement just yet, but this would be a sufficient problem for me to reject it at the end of my trial, and I would prefer to have found a really useful tool with no issues and to go on to buy the licence.
I just took a look at the configruation of VS and R# because in the past there where interferences between Visual Studio and R# formatting of VB code.Surprisingly i can't reproduce the iussue. But i just installed the latest bugfix release R# 2020.1.3 and the current Visual Studio Release 2019.6.0.
Thanks for the reply. I have now upgraded to R# 2020.1.3 to see if that makes any difference; and installed the JetBrains Toolbox in the hope that it will alert me as to future updates being available. I can't upgrade VS because I am required to use the 2017 Community Edition but all available updates that I know of have been applied. So let's see what happens.
Yesterday, in desperation, I switched off R# from within VS and rebooted and restarted VS, but I am still having performance issues. As a developer, my first thought is always "what has changed" and the only change on my system was to install R#. So I remain suspicious for now.
Having done the update to R# it is now active once again.