Visual Studio 2003 .. frustrations

  • Thread starter Thread starter Sahil Malik
  • Start date Start date
You are using VS 2003. This is just one of the many problems with this IDE.
There is a newsgroup dedicated to the IDE and this is a common problem. The
fact that MS does not see fit to update the IDE but make it's customers wait
for the next release is turning me against them. I have had to reinstall
the IDE 4 times to get it back to running.

Perhaps if all developers who have problems with the IDE were to post in the
IDE newsgroup they might do something.

microsoft.public.vsnet.ide

Lloyd Sheen
 
Hmm .. so uninstalling and reinstalling the IDE will fix this? Might be
worth the effort frankly .. right now it's like I get 5 minutes to make my
changes to the code, because after that the IDE goes into a stupor.

- Sahil Malik
Independent Consultant
You can reach me thru my blog - http://dotnetjunkies.com/WebLog/sahilmalik/
 
You are using VS 2003. This is just one of the many problems with this
IDE.
There is a newsgroup dedicated to the IDE and this is a common problem.
Click to expand...

The OP did mention that it was a C# project. In VS 2K3 I have observed that
all the "intelli*" features get all wigged out when I have some subtle
syntax issue, like a missing ; or forget to "using" some namespace.

Also, another C# issue I have seen is that the blue wavy line that appears
during a build attempt underscoring some problem code, doesn't disappear
when I fix the code, until I do a rebuild.

Each time I have seen this behavior, tracking down and fixing my code error
causes the IDE to resume its normal helpful style.

I just thought I would point that out, in case that's what's happening in
the OP. But I DO really wish the IDE would not do things like that for a
subtle syntax issue.
 
No guarentee that anything would be fixed. I did because my frustration
level was at high. Reinstall was suggested in newsgroup so I tried.
Problem is that the problems seem to come back after a while.

Lloyd Sheen
 
Before you uninstall the IDE, you might want to get rid of or unload all
add-ins. They can cause problems.

Regards,
Frank Hileman

check out VG.net: www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio .NET graphics editor
 
Sahil Malik said:
This is a C# project. My code highlighting decides to dissappear randomly.
With that goes away my intellisense, ability to copy paste, and my sanity.

What is going on?
Click to expand...

There have been some times when quitting out of VS.NET and starting over has
solved the problem for me.
 
Thanks Frank, and everyone else who replied.

Well my approach right now is to open/close the form, restart the IDE,
restart the PC. Strangely enough, it never happens in VB.NET, and it never
happens when no form designers are open.

Highly interesting .. hmm ..

- SM
 
You are using VS 2003. This is just one of the many problems with this IDE.
There is a newsgroup dedicated to the IDE and this is a common problem. The
fact that MS does not see fit to update the IDE but make it's customers wait
for the next release is turning me against them. I have had to reinstall
the IDE 4 times to get it back to running.

Perhaps if all developers who have problems with the IDE were to post in the
IDE newsgroup they might do something.
Click to expand...

prehaps if all you highly paid developers send in a bill to microsoft for
time spent installing their dev-env.

last time my (re)install took 2 HOURS (any reason why). i managed to get
that down to ~1 1/2 hours via following the "install from network"
instructions. but then again it took over half an hour to coy the blody
cd's to my server.

urgh..
 
Sahil said:
Hmm .. so uninstalling and reinstalling the IDE will fix this? Might be
worth the effort frankly .. right now it's like I get 5 minutes to make my
changes to the code, because after that the IDE goes into a stupor.
Click to expand...

I'm working with VS.NET for over 2 years now and for about 10+ hours a day
and have never re-installed any version.

I did see the intellisense dissapear occasionally (in property declarations
mostly) and the color coding feature (in code behind pages of the asp.net
editor) but not that often.

Be absolutely sure you don't install VS.NET 2005 on the same machine, beta
stuff and malicious plugins into your vs.net installation. Often people run
into problems when they installed a beta of a plugin, 'handy .net tool' or
vs.net 2005 on the same box and wonder why vs.net 2003 is crashing all the
time.

Frans.
 
Steven said:
prehaps if all you highly paid developers send in a bill to microsoft for
time spent installing their dev-env.

last time my (re)install took 2 HOURS (any reason why). i managed to get
that down to ~1 1/2 hours via following the "install from network"
instructions. but then again it took over half an hour to coy the blody
cd's to my server.
Click to expand...

The install takes ages because of the small files in all the examples. The
CDFS driver in WinXP has a bug that it doesn't cache paths so it has to
re-read the position where to start after every file. This bug was fixed in
Win2k3. (and yes, still not released to the public, like all those nice other
fixes of .NET 1.1 and vs.net, which sit on PSS' harddrive already for over a
YEAR)

FB
 
Back
Top