Author |
Topic |
|
sosedada
Senior Member
USA
36 Posts |
Posted - Mar 13 2007 : 09:18:03 AM
|
I've never had a problem with them in the past. I found feline's FAQ about changing StdAfx.h (http://docs.wholetomato.com?W310) and did that. I did rebuild my symbol database, I've double checked the path to the StdAfx.h file. Is there a way to see if the new StdAfx got used? Unfortunately, I can't recall which build I was using before 1548, but it was older than 1544.
VA_X.dll file version 10.3.1548.0 built 2007.02.23 Licensed to: VA X: XXX (1-user license) Support ends 2007.09.29 VAOpsWin.dll version 1.3.4.6 VATE.dll version 1.0.6.0 DevEnv.exe version 8.0.50727.762 msenv.dll version 8.0.50727.762 Font: Consolas 13(Pixels) Comctl32.dll version 6.0.2900.2982 Windows XP 5.1 Build 2600 Service Pack 2 2 processors
Platform: Custom Stable Includes: C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\IDE\\include; C:\\eddynet\\opt; C:\\eddynet\\opt\\Qt\\3.3.5\\include;
Library Includes: C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\IDE\\include; c:\\eddynet\\projects; c:\\eddynet\\opt;
Other Includes: C:\\eddynet\\projects; C:\\eddynet\\include;
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Mar 13 2007 : 09:51:49 AM
|
VA 1548 now uses the %USERPROFILE% directories for its symbol database, etc. So this has an effect on the stdafx.h file, see this FAQ:
http://docs.wholetomato.com?W302
Have you looked at your stdafx.h file since installing the new build of VA? The most likely answer is that your changes have been wiped out. The installer ships the new default stdafx.h file, overwriting your changes. This is why in VA 1548 you have the option of keeping your own custom stdafx.h file that the VA installer does not know about and will not overwrite. |
zen is the art of being at one with the two'ness |
|
|
sosedada
Senior Member
USA
36 Posts |
Posted - Mar 13 2007 : 09:57:56 AM
|
I changed my StdAfx.h last week, but didn't rebuild my database until yesterday. I installed 1548 two weeks ago. I followed the 1548-based instructions from the FAQ you linked to. |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Mar 13 2007 : 10:00:07 AM
|
Strange. I will run some tests here. |
zen is the art of being at one with the two'ness |
|
|
sosedada
Senior Member
USA
36 Posts |
Posted - Mar 13 2007 : 11:19:50 AM
|
Thanks. While we're on the subject of Qt, is there a way to have VA ignore my moc_*.cpp files? Its a waste of time and space to parse them. |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Mar 13 2007 : 1:28:38 PM
|
I have found the problem, I listed the wrong path's in the FAQ *oops* I have now corrected them. You need to create the file:
C:\\Documents and Settings\\<USERNAME>\\Application Data\\VisualAssist\\Misc\\StdAfx.h
So remove "Local Settings" from the path.
For the moc files, I just let VA parse them personally, and added -moc to my OFIW filter to ignore them when searching for a file.
To get VA to ignore the files completely you could try using:
VA Options -> Projects -> Extensions -> Extensions to ignore
I am not sure if this will work, but you could try. |
zen is the art of being at one with the two'ness |
|
|
sosedada
Senior Member
USA
36 Posts |
Posted - Mar 13 2007 : 1:36:09 PM
|
thanks, I'll rebuild.
OFIW? |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
|
|
Topic |
|