| T O P I C R E V I E W |
| superzmy |
Posted - Feb 27 2023 : 04:57:15 AM
Some times I copy one entire solution to other dir.
And I edit very much, like I rename an field of a class.
Then I open vax symbol window,
I may see two same file "xxx.cpp" that one in the copied Project, and the other is [External] Project in the old dir.
I use notepad++ to search in the whole dir to ensure that old dir path is not exist in the working dir.
VS F12 can process the symbol well, the duplicated symbol cache looks like belong to VAX.
Should I change the GUID of vcxproj ? |
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Mar 23 2023 : 07:02:32 AM
Are you opening the other directory? VA should not be adding anything from the other directory into its symbol database unless somehow directed to parse and store the information for files from that directory. So I am trying to work out what might be triggering these files to show up in your symbol database. |
| superzmy |
Posted - Mar 23 2023 : 12:14:21 AM
quote:
Originally posted by feline
Have you tried rebuilding your VA symbol database? Unless your solution is VERY large this should only take a couple of minutes, at most, and should fix all of these problems you are seeing.
but days later the other dir will come back. |
| feline |
Posted - Mar 08 2023 : 07:50:43 AM
Have you tried rebuilding your VA symbol database? Unless your solution is VERY large this should only take a couple of minutes, at most, and should fix all of these problems you are seeing. |
| superzmy |
Posted - Mar 08 2023 : 02:58:08 AM
that is useless.
I had done this many times.
even that I delete old dir, and now the symbol in window first line, its file and dir is empty, and if I click it nothing will happen.
Is it possible to give us a filter option to remove symbol by dir ?
When I edit something here and there, I may be guided to the old dir and make bad edition. |
| feline |
Posted - Feb 27 2023 : 06:51:31 AM
Can you please try pressing the button:
VA Options -> Performance -> Rebuild symbol databases
which will take a restart of Visual Studio to take effect. VA should know which files belong to which project, so should not list files from a different project, even though the information for several projects is normally stored in our symbol database all at once. But apparently copying the entire solution is confusing us. This will let you start over with a clean symbol database, so no "old" symbol information. |
