VS 2005 IDE stops responding

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi Everyone,
I hope someone else has had this problem. I recently started to use VS 2005
(vb.net) and today alone I have had to close VS 8 times while trying to code.
I have a least 130 controls on this form. I go to the form to get the name of
one of the controls and flip back to the code and paste the name into the
code window. I can do this about 10 times maybe, then suddenly the IDE stops
responding. The cursor switchs back and forth between the arrow pointer to
the 4 arrow cursor. If I click on the form, then I get an hourglass and I
can't do anything after that. I figured it was asving settings or somethine,
but I've let it set there for like 5 minutes, but no change, so I close out
of VS. Sometimes I can close VS using the x button and if I had changes left
it asked if I want to save. It seems to save I think. But this is really
anoying me to death. Is there a setting or something that I can possibly
change to stop all this from happening.
For example, It happened to me before I wrote this message, I opened IE,
logged into here, and at this point I still have the hourglass. At last 4
minutes have passed. Now if VS needs that much time to do saving or updating
of a form or what ever the &*#%$#$ it is doing, I will be seriasally be
considering going back to VS 2003. Did they release this product to soon?
Thanks for all the help.
Michael
 
Personally, I think so. I have had several issues that I have to go through
MS support to already.
The IDE is very slow for me as well, and locks up all the time - although I
can wait it out, and it is responsive again. But very often just
Intellisense, or loading up a form in the designer, etc, takes far far too
long.
 
I have had some problems with vb.net 2003 but it is infrequent and only locks
for a minute or so. Appreciate your helping me make my decision NOT to
upgrade to 2005 until I start to see some positive comments on it in the
newsgroups.

It apparently has some nice features but also has some serious
problems...maybe SP1 or SP2 when they come out will make it worth upgrading.
 
Michael,

I have the same expirience. When this happens (beside the first time the
references are set), than I take another tab and go back. Strange enough it
is than responding direct.

Cor
 
Happens to me too. But it does not take 130 controls
to produce the result. My form only has a dozen or so and
it happens once in a while.

One of those controls, however, is a 9,000 line usercontrol.

I find that if I make sure everything compiles ok, it is
normally ok to open a form in the designer. Opening a
form which is hosting a buggy usercontrol seems to be
a big no-no. Unlike my Ctrl-F problem (see my post of
Dec 14th), I have not found a way of consistently
reproducing the form editor problem, though.

Would like to hear from anyone who knows what causes
the problem so I can avoid it.

I often just create my controls through code, thereby
avoiding designer problems altogether, but for some forms,
this is just not a sensible way of working.

For now, I have just gotten used to hit "Save All",
closing as many code windows as possible, and compiling
the program (esp. if it contains usercontrols) before opening
the forms designer, but not knowing the cause of the
problem, I have no idea if it makes any difference at all.

/JB
 
Back
Top