No problem -tz-. The VA db is rebuilt whenever the version number changes. Further, for VS2010 and VS2012, the db is stored in the install dir; when you do an update, the install dir including the db is removed.
We've got Chris and -tz- in the support system and are continuing there. I tried contacting jonnygarrett but the mail bounced. Mail was also sent to Steve. Anyone else that experiences this problem should contact us directly at http://www.wholetomato.com/support/contact.asp
This is now happening to me as well. I tried to rebuild the symbol DB but that resulted in only 8 (yes 8) files showing up in the OFIS list where we normally have 5000. Any help here would be appreciated.
VA_X.dll file version 10.7.1936.0 built 2013.04.22 DevEnv.exe version 11.0.60315.1 Ultimate msenv.dll version 11.0.60315.1 Comctl32.dll version 6.10.7601.17514 Windows Server 2008 R2 6.1 Build 7601 Service Pack 1 8 processors (x86-64; WOW64) Language info: 1252, 0x409
To anyone getting this bug, the only ways I've found so far to prevent it are to either (1) use Visual Studio 2010 or (2) use Visual Assist 1916 or earlier.
Visual Assist 1929 and Visual Assist 1936 both get this bug intermittently when using Visual Studio 2012.
In the meantime, a workaround for the problem when it occurs is: - File | Close Solution - del *.va from Data\\vs11_?\\ProjectInfo directory of the VA install directory ( http://docs.wholetomato.com?W282 ) - reload solution
Sorry to hear that. We've gotten reports from others that the problem is fixed.
Does changing the value of CacheProjectInfo (at HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VANet11) to 00 prevent it from happening (exit all instances of VS before modifying registry)?
Open File in Solution missing files
Posted - Apr 24 2013 : 11:22:19 AM
