From the topic titled "VA searches symbols in unrelated files" it states "When you open a code file that is not part of the solution VA parses it."
Sometimes I will view a source file that is not related to the current solution and I really don't want these files parsed. It just causes confusion when I use Goto (ALT+G) later.
As an example, sometimes I'll view a file from the history of source control. VS will place this file in a Windows temp directory but VA X parses it.
And sometimes, I'll create a quick prototype of a class file, that's never added or used in the project or solution. But VA X remembers it.
I would just rather have VA X stick only to the files relevant to the solution and projects I am trying to build.
This makes sense. Are you aware that telling VA not to parse these files is likely to stop VA syntax highlighting working in these files? I am just checking that the cost is reasonable.
Good to know, and I suspect others would also accept this trade off, I just wanted to check. I have put in a feature request for this, it is an interesting and helpful idea:
What source control do you use? VA knows about temp file naming conventions used by Perforce and Subversion and explicitly ignores files they create in the temp dir. If the source control you use has a naming convention for temp files we can support it like Perforce and Subversion.
Prevent parsing of non project/solution files
Posted - Feb 19 2013 : 10:09:38 AM
