Editing C# Painfully Slow

[James]

I compile my code, I get a few errors, I go to the 1st error in the editor
and start to type in the correct code and I get no where because with each
key stroke the caret goes away, then a long pause and then the carey comes
back showing one character entered so it's like this::

SomeObject.D ... long pause ... SomeObject.Do ... long pause ...
SomeObject.DoS ... long pause ... SomeObject.DoSo ... long pause ...
SomeObject.DoSom ... long pause ... SomeObject.DoSome ... SomeObject.DoSomet
.... SomeObject.DoSometh ... SomeObject.DoSomethi ... SomeObject.DoSomthin...
SomeObject.DoSomething

so it litterally takes me 5 minutes to type in SomeObject.DoSomething .
How do I get this to speed up?

thanks,

JIM

 

[clintonG]

I've had this exact same phenomena using VS2005. Two steps were required to
restore reasonable performance noting VS2005 is clearly a slothful pig
anyway.

1.) Make sure I had no previous instances of any .NET Framework beta.

2.) ** Exit VS2005.
** Log to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary
ASP.NET Files
** Delete the folder for the project(s).
** Reload VS2005 and rebuild. Performance should be restored.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/

 

[Susie DBA [MSFT]]

yeah I've had awful performance form visual studio 2005

but i'm sure not using ASP.net

are there other explanations for this??


it makes my whole machine run like crap; I can't believe how bad VS
sucks

 

[gregarican]

yeah I've had awful performance form visual studio 2005

but i'm sure not using ASP.net

are there other explanations for this??

it makes my whole machine run like crap; I can't believe how bad VS
sucks








- Show quoted text -

What are you running VS 2005 on? Just curious. I've run it recently on
a Dell notebook PC from 2001 that's a 800 Mhz CPU with 512 MB RAM on
it. It wasn't the fastest gun in the west but it wasn't that painful.
Then I upgraded to a new Dell notebook PC with a 1.8 GHz CPU and 2 GB
RAM. A heck of a lot faster. Both of these notebook PC's have Windows
XP SP2 on them. As for running things in Windows Vista, I had to
configure and ship a new Dell notebook PC with the same 1.8 GHz CPU
with 2 GB RAM and almost all apps under Vista crawled. I would run
them side by side with my Windows XP SP2 notebook PC and the XP one
ran things seemingly twice as fast...

 

[RobinS]

It's our neighborhood troll.

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

 

[Susie DBA [MSFT]]

you do understand the difference between the p4 1.8 and a pentium
mobile 1.8 right?

p4 1.8 = the worst chip ever (all p4s under 2.0 ghz sucked)

p mobile 1.8 = a p3 clocked up to 1.8 -- which is a great processor

and your 800mhz.. it's one of those 'ultra low voltage' things?
because i'd take one of the recent 800 mhz ultra low voltage against
something quite a bit faster.

so it could be that many 800mhz machines ARE faster than a 1.8ghz for
example
I know I'd rather use a straight p3 800mhz vs a p4 1.8.. any day of
the week!

I'm just amazed how poorly visual studio runs.. in general my boss has
a centrino duo.. I think that it's technically a core 1 duo-- with
1gb ram.. and this ASP.net solution that we're all working on-- it has
about 50 ascx files and maybe a dozen pages?

it takes like literally 5 minutes to open

it makes me sick to see it... the people at Microsoft should stop
throwing away year old computers and start testing their apps with a
decent configuration.

I mean seriously-- throwing away old hardware is not smart.. Making
better software that constantly runs faster and faster and faster?

It shouldn't be that difficult.

but the bottom line is that M$ doesn't give a crap about
performance.. I find it ridiculous that Visual Studio takes 5 minutes
to launch ANYTHING.

I mean get real.

I just know-- that Microsoft's programs-- their whole company-- is
going to hit a brick wall when then can no longer tell people to 'just
add more ram'

I mean.. the 2gb limit is HERE!

-Susie

 

[James]

Thanks, this helped but I think my main issues is that the Conversion of my
Forms and Controls from 2003 .Net 1.1 to 2005 .Net 2.0 left my designer code
intact inthe original files, so by splitting them out to partial classes
i.e. .Designer.cs may be the ticket.

JIM

 

[Andy]

you do understand the difference between the p4 1.8 and a pentium
mobile 1.8 right?

p4 1.8 = the worst chip ever (all p4s under 2.0 ghz sucked)

p mobile 1.8 = a p3 clocked up to 1.8 -- which is a great processor

and your 800mhz.. it's one of those 'ultra low voltage' things?
because i'd take one of the recent 800 mhz ultra low voltage against
something quite a bit faster.

so it could be that many 800mhz machines ARE faster than a 1.8ghz for
example
I know I'd rather use a straight p3 800mhz vs a p4 1.8.. any day of
the week!

I'm just amazed how poorly visual studio runs.. in general my boss has
a centrino duo.. I think that it's technically a core 1 duo-- with
1gb ram.. and this ASP.net solution that we're all working on-- it has
about 50 ascx files and maybe a dozen pages?

it takes like literally 5 minutes to open

it makes me sick to see it... the people at Microsoft should stop
throwing away year old computers and start testing their apps with a
decent configuration.

I mean seriously-- throwing away old hardware is not smart.. Making
better software that constantly runs faster and faster and faster?

It shouldn't be that difficult.

but the bottom line is that M$ doesn't give a crap about
performance.. I find it ridiculous that Visual Studio takes 5 minutes
to launch ANYTHING.

I mean get real.

I just know-- that Microsoft's programs-- their whole company-- is
going to hit a brick wall when then can no longer tell people to 'just
add more ram'

I mean.. the 2gb limit is HERE!

Hmm, VS seems to run fine on a laptop I bought in 2001. I suspect its
your machine that's the problem, and a bunch of junk running that you
don't need. There are certain areas were VS runs slow, but not just
editing a text file.. certainly responsiveness could be improved by
better use of threading for long running tasks. Most other slow
downs are simply disk I/O related.

The 2GB limit is here and already gone; 64 bit computers have been out
for a while now and that seems to be where we are heading. For
example, Exchange 2007 will only run on a 64 bit operating system. My
home system is a few years old and will support 4GB once I move to a
64 bit OS.

 

[RobinS]

Hmm, VS seems to run fine on a laptop I bought in 2001. I suspect its
your machine that's the problem, and a bunch of junk running that you
don't need. There are certain areas were VS runs slow, but not just
editing a text file.. certainly responsiveness could be improved by
better use of threading for long running tasks. Most other slow
downs are simply disk I/O related.

The 2GB limit is here and already gone; 64 bit computers have been out
for a while now and that seems to be where we are heading. For
example, Exchange 2007 will only run on a 64 bit operating system. My
home system is a few years old and will support 4GB once I move to a
64 bit OS.

He's our neighborhood troll.

Robin S.

 

[Susie DBA [MSFT]]

Andy

you're full of shit

it doesn't RUN FINE

you just don't build complex apps.

My boss has a brand new Core 2 Duo machine; 2gb ram.. and she's
building this silly ASP.net app-- it takes FULLY FIVE MINUTES to
preview a page in ASP.net

it's goddamn ridiculous

C# is bloatware, .NET is bloatware

the only solution is to go back to a real-mans IDE

VB6

you don't need to build Objects-- which everyone agrees MAKES YOUR
CODE RUN SLOWER
you don't need a crutch for XML and web services-- web services don't
feed starving kids; web services don't make data entry FASTER

what we need is simple data entry apps

**** INFOPATH
**** SHAREPOINT
and **** C#

MICROSOFT SHOULD HAVE FOCUSED ON VB INSTEAD OF SPREADING RESOURCES AND
BUILDING NINETEEN VERSIONS OF THE XBOX AND VISUAL STUDIO

 

[Susie DBA [MSFT]]

and x64 is already a market failure

you dipshits need to start specifying the difference between '64 bit'
and x64

64 bit has been around for a decade.
x64 has NO DRIVERS

so **** Microsoft

they need to stop building BLOATWARE instead of trying to shove 16gb
of ram down our throats

 

[Susie DBA [MSFT]]

most slow downs are simple disk I/O related?

I don't know what ****ing planet you're from

but MS builds bloatware; and it's mother ****ing time for them to get
to work and start building a decent IDE

Everything I've looked at-- from Visual Interdev to Business
Intelligence Development Studio _SUCKS_BALLS_
I mean seriously here

MS lost the war when Adobe bought Macromedia
Now; I can only hope that Adobe is bought by Oracle so that _SOMEONE_
makes a decent IDE this next decade

 

[Susie DBA [MSFT]]

'a bunch of junk running that we dont need'

LIKE THAT IS OUR FAULT?

Ms is out, trying to CON us into .NET instead of making IE secure
and you say that it's OUR FAULT that Windows CATCHES A COLD
_EVERYWHERE_?

stick a cork in it, M$ fanboy; go play with your barbies and sissy-ass
programming language

'oh how trendy M$ came out with a cute little name for a programming
language; let's just change EVERYTHING to a new language just because
MS used the letter #'

GAG

**** C AND **** SHARP

AND **** MICROSOFT

 

[Andy]

He's our neighborhood troll.

Ahh... thanks for the tip Robin. First time I've seen a troll here..

 

[RobinS]

Yeah, he has a bunch of aliases; he used to hang out over in the VB group.
What's impressive is that you managed to invoke not 1, not 2, but *4*
responses to your posting. THe most I've ever seen is 5, and only once. So
that's pretty good. ;-)

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