void felineTestDotEnter()
{
	std::string *pStringForDot;
	// type dot in this comment, and after "pStringForDot" below
	pStringForDot;
}

quote:

---

Originally posted by feline

Does disabling VA have any effect on these problems?

---

quote:

---

Are you working just in C++, or in different languages as well? When you say moving between debugging and editing mode, are you getting the IDE to apply code edits without doing a full recompile?

---

quote:

---

Can you please look and see if you have the setting:

IDE tools menu -> Options -> Environment -> Documents -> Show Miscellaneous files in Solution Explorer

turned On or Off?

---

quote:

---

If this is turned On can you please try turning it Off, and see if this makes any difference?

Also, do you have the Incredibuild IDE extension installed? This could also be a factor.

---

quote:

---

I am not aware that we have "fixed" this problem in the last few months, but I was not aware this problem had come back again to be fair.

---

quote:

---

Originally posted by feline

Let's focus first on Alt-Shift-R not working reliably, since this is something you can trigger on demand.

Is this still mapped to VA's Rename refactoring, or have you changed the keyboard mapping?

---

quote:

---

Assuming this is still mapped to VA's Rename refactoring, can you please place the caret into a comment block, and into a word in a comment, and press Alt-Shift-R again. You should get the same warning tone from your computer, to tell you that the command is not available here. I just want to check that we are seeing the same basic behaviour in a normal situation.

---

quote:

---

When Alt-Shift-R is failing to trigger the VA Rename dialog on a symbol in your code, what, if anything, is VA showing in its Context and Definition fields? These are normally found at the top of the editor, and are where the Alt-M list appears from.

---

quote:

---

VA should be showing you information about the symbol that the caret is placed into. However, if VA is showing you nothing, or the wrong information, it would explain why Alt-Shift-R is not working. This should only happen if our parser is confused by something in your code, or we have not had time to finish parsing your latest edits. In either case, if VA does not know what the current symbol is, we cannot offer to rename it.

---

quote:

---

If this is what is happening, instead of restarting the IDE, can you please just move the caret to a different symbol, and see if Alt-Shift-R works there? Also please try Alt-Shift-F for Find References. This should show a message box stating that "Find References is not available because the symbol is unrecognized" if it is not available.

---

quote:

---

After testing this, move the caret back to the "problem" function name, and try again. Are the VA context and definition field being updated correctly? Is either command working on this function name?

---

quote:

---

Originally posted by feline

Apologies, I got side tracked by trying to pin down something that sounded easier to track. I don't recognise the symptoms and problems you are seeing here, which suggests there is something unusual about your situation.

Can you please close all instances of the IDE and then run the command:

"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest

If you are not running the Professional version of VS2019 you will need to edit the path to the version you are using. This will create and load a new, default IDE profile. This new default profile will only have the default extensions installed, and none of your settings. After loading this you can install VA from the online extension store:

IDE Extensions menu -> Manage Extensions

just doing this, using the default IDE and VA settings, can you see if you still get the same problems?

To return to your normal, default profile, just close the IDE and load it again normally.

To return to this test profile just re-run the command line above, with the command line switch.

You can export your IDE settings from your main profile and import them into the test profile if you want as well, which will be an interesting test, to see if the problem reappears.

---