| Author |
 Topic  |
|
|
mikes
New Member
4 Posts |
 Posted - Jun 09 2006 : 2:44:09 PM
|
Hello all,
First I'd like to say how much I like VSX. It's a great productivity tool!
I've encountered a problem with our install of VSX where it seems to ignore my suggestion that it not parse .tlh files. Assuming there is nothing unique about .tlh files, in the context of "Extensions to ignore", this would apply to other extensions as well.
The steps I followed to produce this problem are:
1. Open Visual Studio (no solution open).
2. Open the Visual Assist X Options dialog. Add .tlh to "Extensions to ignore" under Projects->Extensions.
3. Click "Rebuild" and "Clear" under Performance->General.
4. Click OK and restart Visual Studio.
5. Open a solution containing .tlh files.
In my case, after following step 5 it takes 10-20 seconds to parse the files in my "Stable include files" and then several minutes parsing the files in my project directories; the vast majority of time is spent parsing .tlh files. These .tlh files are usually ~3-5 megs each and present in nearly every project in the solution. Since they are regenerated quite frequently and some of our solutions have a large amount of projects this adds up to a lot of CPU time spent parsing.
Here are some images illustrating the problem:
If anyone has any suggestions on how I can prevent VSX from parsing particular file extensions I would love to hear them.
Thanks,
Mike.
|
|
|
mikes
New Member
4 Posts |
Posted - Jun 14 2006 : 2:14:38 PM
|
| Would someone from whole tomato please comment on this. |
 |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jun 14 2006 : 2:27:27 PM
|
| The tooltip in that control is incorrect. The option does not prevent VA from parsing files that are part of your solution. It prevents VA from being active (suggestions, listboxes, autotext, context and definition windows, HCB updates, methods in file) in editor windows for those file types. |
|
|
|
mikes
New Member
4 Posts |
Posted - Jun 14 2006 : 6:17:37 PM
|
So the user interface is advertising functionality that simply isn't implemented? I'll have to remember that one next time I get a bug report. ;)
I guess WT can call this a feature request then. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18993 Posts |
Posted - Jun 14 2006 : 6:26:42 PM
|
i think the interface is its self the bug, in this case 
case=1318
have you looked at this FAQ
http://www.wholetomato.com/support/faq.html#extension
on telling VA about new file extensions via the registry? you may be able to do this in reverse, to stop VA looking at the .tlh files. i have not tried this myself, i am not aware of having any massive .tlh files on hand to test with, but this might work. |
zen is the art of being at one with the two'ness |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jun 14 2006 : 6:48:46 PM
|
| You might also try moving .tlh from the VA header file list (ExtHeader) to the source file list (ExtSource) at HKEY_CURRENT_USER/Software/Whole Tomato/Visual Assist X/VANet. |
|
|
|
mikes
New Member
4 Posts |
Posted - Jul 13 2006 : 6:58:33 PM
|
sean,
Moving .tlh into ExtSource wouldn't work, but moving it into ExtBinary did the trick. |
|
|
| |
Topic |
|
Bug Report: "Extensions to ignore" ignored.
