Intellisence Doesn't Remember Last Session
I have visual studio 2003 installed on my computer. The intellisense was working just fine until I installed VS 2005. I don't know what happened but now everytime I start VS 2003 it doesn't remember any of the recent intellisense commands.
Ex: If I type "System." it should come up as "System.Diagnostics" instead it selects the first item in the list. If I repeat the process in the same session it goes right to "System.Diagnostics".
Is there anyway to fix this?
Evan,
The feature that you're describing is "most frequently used" (it's been changed in VS 2005 to most recently used). The state of the most frequently used cache is persisted in a file called '.projdata' in VS 2003. It's persisted per project. In this case, are you opening the same project that you were using before? This feature can also be disabled in tools | options - check Tools | Options | Text Editor | C# | Advanced (if I remember correctly) and look around for an option with wording like "IntelliSense pre-selects most frequently used."
-Anson
Evan,
Can you try the following steps?
- Create a new C# Console Application
- Type Console.Write (select WriteLine in the completion list by hitting the down arrow and hit enter)
- Type Console. and verify that WriteLine has a dotted outline around it
- Close the solution and save it
- Open the same project and type Console.
Does WriteLine have a dotted outline around it, or does Equals?
Thanks!
Anson
Evan,
I just want to make sure that we're talking about exactly the same thing. You're seeing the behavior in VS *2003* after intstalling VS 2005 correct? You're not using VS 2005?
In VS 2005 the MFU behavior has been changed to MRU. We don't persist MRU between sessions. However, VS 2005 should have no impact on VS 2003 (if you're running them side-by-side). Did you recently install the VS 2003 service pack?
-Anson
I have both VS 2005 and VS 2003 installed. I haven't actually used 2005 yet.
I don't have the SP1 installed. I am running version 7.1.6030.
This issue started soon after I installed 2005. I did have trouble with the install because of the messed up burnt CDs that wouldn't locate the file correctly.
Evan,
Is this the only issue you're seeing with your VS 2003 install? I've been trying to come up with a scenario in which an install failure of VS 2005 would cause the MFU behavior in VS 2003 to change... and I haven't been able to. Given that you had the install failure (do you happen to remember what it was?), I would suggest repairing your VS 2003 install. I don't see how that would help, but then, I currently don't have any ideas about what would be causing the interaction.
Anson
