VA_X.dll file version 10.1.1293.0 Licensed to: VA X: <snip> (5-user license) Support ends 2005.07.09 VA.NET 7.1: VAOpsWin.dll version 1.2.0.4 DevEnv.exe version 7.10.3077.0 msenv.dll version 7.10.3077.0 Font: Courier New 13(Pixels) Comctl32.dll version 5.82.2800.1106 WindowsNT 5.1 Build 2600 Service Pack 1 Single processor
Platform: Win32 Stable Includes: C:\\dev\\trunk\\<snip> C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include; C:\\dev\\trunk\\<snip>
Library Includes: C:\\dev\\trunk\\<snip> C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl; C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src; C:\\dev\\trunk\\<snip>
I'm not sure how additional dictionaries get installed. I didn't do anything special. Does it run off of the dictionaries with Microsoft Office or something? If so, I have Office 2003 installed, if that makes a difference.
Is there something I can check to determine what dictionaries are in use?
just to complete the picture i see this bug in .NET 2003 on a VM Ware machine, but not in .NET 2003 on my main machine, with the same version of VAX and the same comment *rolls eyes*
there must be a trigger, but so far i have not found it.