VS2005 code editor stays in runtime

[Bryan]

I am developing a VB project in VS2005 that has SP2 installed. This
is the process that is causing a problem:
Open VS2005, open the project
Write some code in the code editor
Run the project in debug mode, test some of the forms
Close the main form which returns me back to the VS2005 code editor
*At this point, when I type anything in the code editor, parenthesis
are inserted after every letter I type. Also I can't backspace past
two characters. In general, the code editor is trying to autocomplete
the expression after every character that I type. It is like it still
thinks it is in runmode or something.
I have to exit the project, then reopen it for this behavior to stop.
Has anyone else experienced this? Have any suggestions?

Bryan

 

[RobinS]

When you are returned to the Code Window, look up at the debug stuff in the
menu bars on the top at the VCR controls for the debugger. Is the play
symbol clickable? If so, then the app is not still running. Or is the
square symbol clickable? If so, then your app *is* running.

I've never seen anything like that.

Robin S.

 

[Bryan]

When you are returned to the Code Window, look up at the debug stuff in the
menu bars on the top at the VCR controls for the debugger. Is the play
symbol clickable? If so, then the app is not still running. Or is the
square symbol clickable? If so, then your app *is* running.

I've never seen anything like that.

Robin S.

The play symbol is clickable. I type one character, lets say 'm', and
this happens:
m()
Then I press another character, lets say g, and this happens
m(g)
After that, I press any number of characters and the following happens
m(g)abcdefghij
The whole time, the code editor is underlining the expression as being
an error, it analysis it after each character stroke, instead of its
usual behavior, which is to check the syntax after you press 'enter'
or space.

 

[Bruce W. Darby]

This may seem a silly question Bryan, but do you have the VS2005 SP 1
installed? Also, were you running any of the Beta's prior to updating?

Bruce

 

[RobinS]

I don't suppose you're having this problem in any of your other apps, are
you? Couldn't be the soda pop you spilled in the keyboard making you Enter
or Tab key sticky?

Robin S.
-------------------

 

[Bryan]

This may seem a silly question Bryan, but do you have the VS2005 SP 1

installed? Also, were you running any of the Beta's prior to updating?

Bruce

I don't suppose you're having this problem in any of your other apps, are
you? Couldn't be the soda pop you spilled in the keyboard making you Enter
or Tab key sticky?

Robin S.

Yes SP1 is installed. No betas running at any time. Brand new
keyboard conisidently! This happens in any project, not just a
specific one.
Do I have to explicitly call an exit procedure when my main form
closes?

 

[RobinS]

Yes SP1 is installed. No betas running at any time. Brand new
keyboard conisidently! This happens in any project, not just a
specific one.
Do I have to explicitly call an exit procedure when my main form
closes?

If you double-click on MyProject, then click on the Application tab, what
is Shutdown mode set to? Mine is set to "When last form closes" so it
doesn't end until all the forms are closed. You can also set it to "When
startup form closes".

Also, check in the Immediate Window to see if all your forms are closed,
like Debug.Print(My.Application.OpenForms.Count), when it's exhibiting this
weird behavior.

It sounds like it's stopped, or you wouldn't be able to hit the Start
button. If you show the debug toolbar (View/Toolbars/Debug) so it shows all
the time, is the square (that is used to stop the application when it's
running) clickable when it's exhibiting this weirdness?

Robin S.

 

[Bryan]

If you double-click on MyProject, then click on the Application tab,
what

is Shutdown mode set to? Mine is set to "When last form closes" so it
doesn't end until all the forms are closed. You can also set it to "When
startup form closes".

Also, check in the Immediate Window to see if all your forms are closed,
like Debug.Print(My.Application.OpenForms.Count), when it's exhibiting this
weird behavior.

It sounds like it's stopped, or you wouldn't be able to hit the Start
button. If you show the debug toolbar (View/Toolbars/Debug) so it shows all
the time, is the square (that is used to stop the application when it's
running) clickable when it's exhibiting this weirdness?

Robin S.

I tried both shutdown modes, neither help. My application is exiting
with code 0, so there are no errors as far as the CLR is concerned.
everything exits fine. I'm thinking of reinstalling, or installing
SharpDevelop
Bryan

 

[Pritcham]

Hi

I had issues like this a while back - exactly as you describe here and
it drove me nuts. From memory I think it was actually nothing to do
with Visual Studio itself but with one of the Add-ins I had loaded -
you might want to check those if you have any (disable them one at a
time to see if the error goes away then you'll know the culprit).

Hope that helps
Martin

 

[Bryan]

Hi

I had issues like this a while back - exactly as you describe here and
it drove me nuts. From memory I think it was actually nothing to do
with Visual Studio itself but with one of the Add-ins I had loaded -
you might want to check those if you have any (disable them one at a
time to see if the error goes away then you'll know the culprit).

Hope that helps
Martin

I wish that was it, but I don't have any add-ins installed.

 

[RobinS]

Hvae you tried this on a different machine? Is it your version of Visual
Studio, or your code somehow?

Have you tried putting in a breakpoint at the Form_Closing of your last
form, and then stepping through to see if it's doing something?

Robin S.
--------------------------------

 

[Bryan]

Hvae you tried this on a different machine? Is it your version of Visual
Studio, or your code somehow?

Have you tried putting in a breakpoint at the Form_Closing of your last
form, and then stepping through to see if it's doing something?

Robin S.

I have done some more research into the problem to find a strange
pattern. First of all, I am using components from Developer Express,
such as a data grid and some command buttons. Here is the pattern.
If I am editing code, then press start while the active tab is a code
editor, and then upon program exit I try to type in the code editor,
the problems arise. however, if my active tab is a form designer when
I press start, then upon program exit I make the active tab the code
editor for that form, the problems do not happen.
It appeared that I needed to be looking at a form designer when
starting my project to avoid the bug. But it gets stranger.
If the active tab when starting the program is a code editor, then
upon program exit I immediately switch to the form designer of said
code, then back to the code, the problem does not happen.
If the only tab open is a code editor, the problem never arises.
Why would the form designer be messing with the code editor portion of
the IDE?

Bryan

 

[Stephany Young]

Does the behaviour occur in an app where you do NOT use any of the Developer
Express components?

 

[RobinS]

I'm going to answer this, because Bryan and I did some back-and-forth
e-mail. It did turn out to be a problem with his plug-ins, and not related
to his code or to Visual studio. He got a hot fix for it, and his problem
is resolved.

Robin S.
---------------------------------------------