I'm using the VB Editor in VS 2005 RTM version and every so often it starts misbehaving and I have to close all editor windows to get working properly again.
What happens is that as soon as I type a single letter at the beginning of a line it immediately appends open and close parens. So for example if I want to type an If statement, as soon as I type 'i' it changes it to i(). If I backspace to delete the parens it puts them back in.

VS 2005 RTM Weird Editor Behavior
Howard Yu
Any clues you can provide will be much appreciated. Meanwhile, we are going to activate the bug that we were unable to fix prior to shipping Visual Studio 2005 and hopefully by fixing this we will also be addressing your issue.
If in the meantime you keep encountering this issue try things like closin and reopening the file to see if the problem goes away. Or closing reopening the project. I realize this is a pain and if it becomes too much trouble you will probably be better off turning Pretty Listing off as previously suggested. Also with Pretty Listing off I believe that issuing a "Format Text" command on your selected text will manually force pretty listing of your code. It's under the Edit Advanced menu.
I hope this helps address your problem.
Cameron McColl
The Wee Scot
kmax
--Matt--*
fedeburin
Matt,
Thank you for the info but from your response it appears that you haven't read the entire thread. I was complaining about a problem I have where as soon as I type a single letter, the IDE turns it into a method call by appending parens to it. I was asked to provide steps to reproduce it which I did.
Arthur Knight
I am a dev on Matt's team and we did encounter this once and were unable to get a repro on the cause. Would you be willing to send me a zip file of your project and any instructions on how to get the situation to occur
We'd really like to find the root cause of this problem as it is obviously very annoying.
Meanwhile if the problem becomes really bothersome a temporary workaround is to disable PrettyListing in the Tools Option section. It's under the Editor -> VB Specific section.
Feel free to contact me directly at cmccoll@microsoft.com
Cameron McColl
The Wee Scot
ETUX
Rob Cannon
I moved your thread to the VB IDE forums. They should be able to assist you better here.
Thanks,
Dylan
loosie
OK, the following is the version info from the About Box.
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41620
Microsoft Visual Basic 2005
The project type is Windows Application and I am using source control.
Dens
Oh the pain
Hi Zisha,
The bug was resolved as No Repro because we have not been able to reproduce this issue, and we don't have sufficient repro steps to help us do so. Thus, we are tracking the issue, but are not reactivating the bug until we have more actionable information.
It sounds like you are running into this bug a fair bit. Thus, we would love to talk with you further about it, so that we can find a repro. Once you have any more information, can you please reactivate the bug at the following location and add your comments there
http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=49e48f9e-6f26-4c8a-9ae5-f8dee8081e66
More details about the particular moment when this bug tends to occur or a sample of your code, would all be useful information.
Thanks,
Lisa
dacoty
Maaloul
Hi, Zisha,
That’s right, with VS2005, you can always type in the code file, regardless of the state of the application (debug or otherwise) since we now support edit and continue. Sometimes, what you type might be flagged as a “rude edit” (something we cannot continue past, like adding a public method for example), but beyond those we can even integrate your changes made while debugging. This option can be disabled, if you prefer, from Tools\options, “Show all settings” ->debugging/enable edit and continue. But hopefully you will like it!
Hope this helps,
--Matt Gertz--*
VB Compiler Dev Lead
JohnBBBBBBBB
Hi Zisha,
Thank you for all your efforts following up with us on this issue. We are currently tracking this issue as an MSDN Feedback Ladybug:
http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=49e48f9e-6f26-4c8a-9ae5-f8dee8081e66
MSDN Feedback is the best way for us to get code defect issues looked at by the product team. If you do find that you are able to gather any more info for a repro, please reactivate the bug and enter your comments there.
Thanks!
Lisa Feigenbaum
VB Program Manager
mokeefe
This sounds like a bug that we fixed earlier in the product cycle, so I’m at a loss to explain why you are seeing it now. (Basically, every keystroke is erroneously sending us a “Commit” message and so we do the parentheses, etc.) Can you provide more detailed repro steps so that we can get to the bottom of this For example, the project type, whether or not you are using source code control, etc. I would very much like to find and fix this problem.
--Matt Gertz--*
VB Compiler Dev Lead
Shelly