| Author |
 Topic  |
|
|
episcopus
New Member
7 Posts |
 Posted - Jan 23 2006 : 3:01:07 PM
|
I have been a happy user of Whole Tomato Visual Assist for many years (ok, after they got over the worst perf issues a few years back :)). I recently upgraded to VS2005 and build 1434 of VA.
Now, every so often, VS2005 decides to go into an "Updating Intellisense..." state with a progress bar on the right, which totally brings my machine to its knees. This lasts for a while, and also sometimes even happens in parallel with the Visual Assist parsing of files, which is inefficient to put it mildly.
What is a sure fire way to disable VS2005's intellisense so I only rely on the VA tool? I went through and unchecked all the settings mentioned in the following article:
http://msdn2.microsoft.com/en-us/library/ecfczya1.aspx
But it still seems to happen from time to time.
Or is that a requirement for running VA? I am using this with a large 2.2 MLOC C++ project. |
|
|
support
Moderator
5029 Posts |
Posted - Jan 23 2006 : 5:13:27 PM
|
VS2005 Intellisense is not a requirement of VA X if you are developing in C/C++ (it is for C# and VB.)
Check out info in this thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=132651&SiteID=1
Another option is to create empty, read-only versions of your NCB files. This works for VS.NET 2003; it might for VS2005. |
 |
|
|
feline
Moderator
United Kingdom
10888 Posts |
Posted - Jan 25 2006 : 6:26:59 PM
|
using a fair sized C++ solution (86 projects) creating a zero length read only ncb file makes no difference *sigh*
VS2005 informs me that it cannot write out the intellisense data it collects, i say "good", and then it proceedes to hammer my CPU into the ground anyway. disabling the options for using intellisense in the IDE's tools dialog did not help either. it would be nice to hear that someone else has better luck with this than i have been having.
another couple of days of this and i am going to try removing the dll the thread speaks about and see what that does  |
zen is the art of being at one with the two'ness |
|
|
|
episcopus
New Member
7 Posts |
Posted - Jan 25 2006 : 6:32:08 PM
|
I finally managed to disable Intellisense - if only by using brute force. 
Follow the following steps and you'll do it too:
1. Make the NCB file in the folder where you store your solution read only.
2. Boot VS2005 and open your solution. Reply “No” to any prompts offering to make the file writable. Because the file is read only, the program will deviously revert to writing to a temp directory file as a fallback.
3. Make the NCB file in the temp folder read only (while VS2005 is open, because otherwise this file is deleted on exiting the app).
4. Close and re-open VS2005.
5. Again, reply “No” to the read only prompt. A message box appears “Intellisense will not be available because the <temp file> is not writable”.
6. Hooray!
I also heard that you can rename “C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages\feacp.dll” and that will also disable the Intellisense processing.
Enjoy! |
|
|
|
feline
Moderator
United Kingdom
10888 Posts |
Posted - Jan 26 2006 : 4:35:04 PM
|
most cool i will try this out soon and let you know. i wondered about the read only ncb file, since the IDE saw it, complained, but then proceded to index my code regardless, leaving me to suspect it was indexing into a non-existent file *sigh*
my only concern with removing the dll is remembering to put it back again afterwards, since i do a small amount of work with C#, where VA does need the IDE's intellisense. |
zen is the art of being at one with the two'ness |
|
|
|
episcopus
New Member
7 Posts |
Posted - Jan 26 2006 : 7:25:35 PM
|
quote:
Originally posted by feline
my only concern with removing the dll is remembering to put it back again afterwards, since i do a small amount of work with C#, where VA does need the IDE's intellisense.
You should just rename it then... |
|
|
|
feline
Moderator
United Kingdom
10888 Posts |
Posted - Jan 27 2006 : 3:04:31 PM
|
i am tempted, but if i do that will i remember what the dll is called in 3 months time when i suddenly discover a need for C# intellisense?
your instructions for the ncb files work perfectly, but understandably doing this breaks the feature that the IDE will colour code in #if 0 #endif blocks for me *sigh* i need to experiment with this a bit, to find out what advantages and disadvantages there are to leaving the IDE's intellisense turned on. at least now i know how to do this  |
zen is the art of being at one with the two'ness |
|
|
|
jpizzi
Tomato Guru
USA
642 Posts |
Posted - Jan 27 2006 : 6:10:35 PM
|
quote:
i am tempted, but if i do that will i remember what the dll is called in 3 months time when i suddenly discover a need for C# intellisense?
Well, you could always rename it something like, "was called feacp.dll" |
Joe Pizzi |
|
|
|
feline
Moderator
United Kingdom
10888 Posts |
Posted - Jan 29 2006 : 2:48:05 PM
|
| picking a new name for the file is easy. being sure i will remember to look in the right directory for the file is the tricky bit |
zen is the art of being at one with the two'ness |
|
|
|
RMdata
Junior Member
17 Posts |
Posted - Feb 02 2006 : 2:58:07 PM
|
feline,
For when using C++,
Why not launch VS2005 with a script or build your own .exe that launches VS2005 after renaming the .dll (if it is not already renamed)
For when using C#,
use the same script or .exe with different commandline parameters that tell it to rename the .dll back to what it is supposed to be before launching VS2005. |
|
|
|
feline
Moderator
United Kingdom
10888 Posts |
Posted - Feb 02 2006 : 5:25:53 PM
|
| i like that, and so obvious when someone points it out this is exactly the sort of thing i do under UNIX, but i am just not used to thinking like that under windows. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Disabling regular VS2005 intellisense?
