IDE problem in vs 2003

S

Sam Marrocco

I'm having a problem while writing code in the IDE for VB.NET 2003. All
is fine, then suddenly the IDE stops auto-indenting code, doesn't
"squiggly-underline" typos, and in general stops handling the text in a
"dynamic" fashion (as you type it and hit return). Clicking in any of
the Tasks or Output windows, then back into the text IDE area forces the
code to reparse, and updates all typos, indenting, etc. The app
continues this way until a restart of vs.net. Then a short time later,
it does it again. This happens on several development machines.

Has anyone experienced this?
 
H

Herfried K. Wagner [MVP]

Sam,

Sam Marrocco said:
I'm having a problem while writing code in the IDE for VB.NET 2003. All is
fine, then suddenly the IDE stops auto-indenting code, doesn't
"squiggly-underline" typos, and in general stops handling the text in a
"dynamic" fashion (as you type it and hit return). Clicking in any of the
Tasks or Output windows, then back into the text IDE area forces the code
to reparse, and updates all typos, indenting, etc. The app continues this
way until a restart of vs.net. Then a short time later, it does it again.
This happens on several development machines.

I remember I experienced something similar some time ago, but it doesn't
occur on a regular basis. Does this phenomenon only occur in a single
solution/project or does it occur with every solution/project? Do you use
any 3rd-party add-ins and extensions for VS.NET on all the machines?
 
N

Nak

Hi there,

I get this irritating bug all of the time using VB.NET 2002 Standard.
The only way for me to cure this is the close the IDE and open it again. I
had first thought that it was a memory issue (or lack of) but I have 512mb
of ram and I would presume that would be enough to run the IDE. How much
ram do you have? It is certainly a strange bug and pretty much renders
VS.NET into and IDE as useful as notepad, the intellisense is what makes it
so good in the first place.

One thing I try not to do now is have more than 1 IDE open at a time,
that usually causes allot of problems for me, in more ways than one!

Nick.
 
G

Greg Burns

Out of chance, do you have a SQL Reporting Services project in your
solution?

Greg
 
S

Sam Marrocco

Nak said:
One thing I try not to do now is have more than 1 IDE open at a time,
that usually causes allot of problems for me, in more ways than one!


Nick,
I regularly use more than one IDE at a time, each with a different
project open, and that has never been a problem. This problem *does*
exist even when only one IDE is used.
 
S

Sam Marrocco

Herfried K. Wagner [MVP] wrote:

Does this phenomenon only occur in a single
solution/project or does it occur with every solution/project? Do you
use any 3rd-party add-ins and extensions for VS.NET on all the machines?

It seems to be related to a particular project; but it's tough to nail
it down:
-It's never happened before I was doing this particular project
-I was doing this project for months before it started happening.
-I haven't had it happen during any other project so far.

I'm tempted to relate it to this particular solution/project. It doesn't
seem to be a particular action that causes it--it just starts to happen.
No third party add-ins/extensions on either machine, just straight vs
2003. I've been attempting to narrow it down, but can't really delete
large blocks of code from the app in order to do so. I'm hoping I'll
stumble on a particular sequence of actions that causes it.
 
T

Terry Brown

Sam,



I remember I experienced something similar some time ago, but it doesn't
occur on a regular basis. Does this phenomenon only occur in a single
solution/project or does it occur with every solution/project? Do you use
any 3rd-party add-ins and extensions for VS.NET on all the machines?

I have experienced exactly this problem very frequently.

It comes and goes within sessions, and with one solution open and one copy
of vs.net running. I have 1GB of ram on my machine and it happens when
vs.net is the only thing running.

I think it is related to vs.net getting confused when you edit code and
create what it thinks is syntactic garbage (even though this is created
only for a moment while you edit). For example, if you edit a line of
code and create an "If" statement without an "End If", it might happen. I
haven't been able to make this happen with a specific sequence of editing
events, but for me, vs.net gets into this state when I am doing this kind
of editing.

It is clearly a bug (or a limitation) in the intellisense parser.

For what it's worth, my installation was originally vs.net 2002
professional, since upgraded to vs.net 2003 professional. I believe the
problem occurred in vs.net 2002 as well, but wouldn't swear to it.

Terry Brown
Stickman Software
http://www.stickmansoftware.com
 
S

Sam Marrocco

There has been showed a crazy bug by Mirza in this newsgroup, can it be that
one?

Interesting....I checked, and couldn't find anything similiar in my
code. Also, the code compiles and runs fine--it's just the IDE that
stops parsing/indenting, etc.
 
C

Cor Ligthert

Sam,

Did you see that message yesterday (I thought) in this newsgroup, where
somebody said that he had cleaned completly all files in his bin directory.

After that you have made a safe copy of course

Cor
 
S

Sam Marrocco

Did you see that message yesterday (I thought) in this newsgroup, where
somebody said that he had cleaned completly all files in his bin directory.

No, I didn't. I just cleaned out the bin directory and worked in the ide
for a bit, and the had the same problem. Ugh.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top