| T O P I C R E V I E W |
| Alexo |
Posted - Feb 08 2010 : 7:10:39 PM
I sometimes search for text in source files on the build machine (can be a different version from the local files in the network)
Today, VA started to suggest symbols from that network folder instead of using the solution when I "find symbol" or "find references".
This persists after numerous restarts of Visual Studio, closing all files, etc. making VA useless (even harmful)
How do I get rid of this behaviour?
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Feb 15 2010 : 11:31:24 AM
Lets start by looking at the Find Symbol dialog box. This has a checkbox "Show only symbols defined in current solution", is this turned on of off? Turning this on should fix the problems you are seeing with this dialog.
When you open a code file that is not part of the solution VA parses it. So it learns about the symbols in this file. However it will forget about these symbols when you rebuild VA symbol database.
So the fact that you were seeing this problem after doing a symbol database rebuild bothers me. Is it possible the IDE was remembering that you had opened files from outside the solution, and it was opening these files when you reloaded the solution? Thus showing VA these unwanted symbols again?
For Find References, if you turn on:
VA Options -> Advanced -> Refactoring -> Display project nodes in Find References results
does this help? Are the unwanted symbols separated out from the wanted symbols? |
| Alexo |
Posted - Feb 10 2010 : 2:59:22 PM
VA_X.dll file version 10.6.1810.0 built 2010.01.22
DevEnv.exe version 8.0.50727.762
VA Options -> Projects -> File Handling -> if Solution is empty -- was ON (now OFF)
VA Options -> Projects -> File Handling -> if Solution is not empty -- was OFF
A non-empty solution was open at the time.
|
| feline |
Posted - Feb 10 2010 : 2:10:29 PM
Which IDE and version of VA are you using?
Do you have either of the VA options:
Upon opening a file, parse all other unparsed files in the same directory:
VA Options -> Projects -> File Handling -> if Solution is empty
VA Options -> Projects -> File Handling -> if Solution is not empty
turned on? |
| Alexo |
Posted - Feb 09 2010 : 12:08:59 PM
That behaviour stopped after a reboot.
However (and this is important!) I am now at a position when just opening a file from the build machine in Visual Studio may necessitate a reboot to make VA work as intended.
Please fix.
|
| Alexo |
Posted - Feb 08 2010 : 7:13:03 PM
Also, I cleaned the temporary symbols and rebuilt the symbols -- nothing helps! |
