VS 2005 freezes during code editing (HotFix 917452)

[Guest]

My development computer (1 gig, XP Home Edition SP2) freezes when I am
editing a very large VB.NET project. It can take minutes to move between a
code pane and the Find and Replace pane. On occasion, it freezes for one or
more hours no matter what I do. I would go back to an earlier version of VS
but I have already invested too much time incorporating features that only
exist in VS 2005.

I have installed the HotFix but it did not do much to help the situation.
To get the compiler to reset itself, I have tried the following in no
particular order.

Reboot
Close with Task Manager
Close normally and reopen VS 2005
Menu Bar>>Build>>Clean Solution

At one time, I started a new project and manually made its contents the same
as the frozen project. That did solve the problem for awhile. Doing the
port was tedious. I wonder if someone knows of code that ports one project
to a new project?

I did split the largest vb file into MyName.vb and MyName.Designer.vb.

I am now going to copy the code for my two largest and most used files to
Word and use the Find feature in Word. When I fnd my point of interest, I
will then locate the code in VS 2005 by using the dropdown boxes. I will not
use the Find and Replace in VB.NET. I think this should help.

Is there a Blog anywhere that is tracking progress on this compiler problem?
I could not find one.

Does anyone have any suggestions for how to make the compiler reset itself,
the things that I tried did not seem to help on a consistent basis. There
does not seem to be a pattern with when the editing becomes functional.

 

[Mythran]

My development computer (1 gig, XP Home Edition SP2) freezes when I am
editing a very large VB.NET project. It can take minutes to move between
a
code pane and the Find and Replace pane. On occasion, it freezes for one
or
more hours no matter what I do. I would go back to an earlier version of
VS
but I have already invested too much time incorporating features that only
exist in VS 2005.

I have installed the HotFix but it did not do much to help the situation.
To get the compiler to reset itself, I have tried the following in no
particular order.

Reboot
Close with Task Manager
Close normally and reopen VS 2005
Menu Bar>>Build>>Clean Solution

At one time, I started a new project and manually made its contents the
same
as the frozen project. That did solve the problem for awhile. Doing the
port was tedious. I wonder if someone knows of code that ports one
project
to a new project?

I did split the largest vb file into MyName.vb and MyName.Designer.vb.

I am now going to copy the code for my two largest and most used files to
Word and use the Find feature in Word. When I fnd my point of interest, I
will then locate the code in VS 2005 by using the dropdown boxes. I will
not
use the Find and Replace in VB.NET. I think this should help.

Is there a Blog anywhere that is tracking progress on this compiler
problem?
I could not find one.

Does anyone have any suggestions for how to make the compiler reset
itself,
the things that I tried did not seem to help on a consistent basis. There
does not seem to be a pattern with when the editing becomes functional.

I had this problem and found that it was a network issue (although doesn't
seem to appear to be one at first). Do you save your project files onto the
network? Do you run SourceSafe or any other source-control system on the
network? Check other possible network issues, for example, check any mapped
drives to make sure they aren't attempting to connect during these delays.

Another possible reason would be a service that is interfering with .Net.
Check your process list to see what is taking up so much CPU cycles and/or
close any un-needed processes to try and isolate the exact cause.

HTH,
Mythran

 

[Guest]

Computer on network in my home. Only other computer on the network is my
laptop which is usually not connected.

I am not running SourceSafe or any similar program. In background are
things like Yahoo Messenger, Outlook, and Norton stuff.

When VS goes comatose, Devenv.exe is taking 100% of CPU. It will flat-line
at 100% for minutes on end.

FYI, in my main form, the Designer.VB has 10,960 lines. The code.vb has
26,599 lines with approximately 5% - 10% comments or remarked out code.

:

See prior message.

 

[Phill W.]

My development computer (1 gig, XP Home Edition SP2) freezes when I am
editing a very large VB.NET project. It can take minutes to move between a
code pane and the Find and Replace pane. On occasion, it freezes for one or
more hours no matter what I do. I would go back to an earlier version of VS
but I have already invested too much time incorporating features that only
exist in VS 2005.

Do you have Edit-and-Continue enabled?

If so, turn it off! There have been numerous reports where this feature
(and the background compilation by devenv that underpins it) simply
/cripple/ a development machine.

Regards,
Phill W.

 

[Guest]

It was on. I had not tried to make this change because when I would go into
freeze mode immediately after loading code and before entering debug mode.
Freeze mode would begin as soon as I went to Search and Relace.

I am now trying with edit and continue disabled. Giving up on-the-fly
editing is a small price to pay in order to minimize the feeze mode. (I do
hate to give it up though)

I will report back in a few days with a comment about my experience. I
suspect that Microsoft will eventually solve this problem.