Re: Dear ms VS.NET 2005 development team
- From: "Carlos J. Quintero [VB MVP]" <carlosq@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Mar 2006 12:27:58 +0100
Dear James,
While I agree that VS 2005 is much slower that its predecessor (except
starting, maybe), there must be something wrong somewhere because 2 GB RAM
should be enough to run it comfortably. I can even use VS 2005 with 512 MB
although it is slow, but with a new CPU and 1,5 GB works much better. If you
have problems even with a simple test winform project, definitely there is
something wrong.
There is a MSDN Product Feedback Center where you can search and post
similar problems, to see if they are acknowledged or fixed:
http://lab.msdn.microsoft.com/ProductFeedback/
If you come with a reproducible performance problem, it may be fixed for SP1
(H2 2006).
Also, there are things that you can turn off like the Edit and Continue,
Refactoring on rename, etc. that will improve the performance.
--
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"jamesd" <jamesd@xxxxxxxxxxxxxxxx> escribió en el mensaje
news:1142994534.321173.158380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dear MS VS.NET 2005 development team,
This is a disappointing product. I work for a large govt department and
EVERY team I work with and know of (over 400 developers) has decided to
stay AWAY from vs.net 2005. I love the new features it offers but this
product simply does not perform as well as vs.net 2003. It blocks/hangs
frequently (not responding) on ALL the machines we have installed it
on, even machines with 3 ghz processors with 2 gigs of RAM.
The main problem is that a LOT of Visual Studio 2005 has been rewritten
from C++ to .NET. What a horrible decision by the VS.NET 2005 team.
Look in the vs.net newsgroups (like this) and everybody agrees it is a
dog. My teams are all sticking with vs.net 2003 because we simply
cannot be productive waiting 3 minutes to compile a simple winform. It
does not matter what hardware you have, huge apps like this in .net
will always be dog slow. Show all the fake stats you want MS, any
product that needs a snappy UI should be written in C or C++. Just wait
for Avalon to come out! Hahaha. No wonder they have decided to not
rewrite big chunks of the OS in .net, nobody will buy such crap. I love
.net, but it should only be used for applications that can handle it.
IDE's should only be written in C++ if they want the developers to be
loyal to it. Programmers are too impatient to put up with slow IDE's.
I am really surprised that such a big blunder has ocurred on MS part,
they should be doing everything they can do to keep people loyal.
Anyways, please consider keeping the most important parts of the
product in c++. You will have a lot more people start using it! Also,
if you know that certain parts of the IDE are causing major perormance
problems, by all means fix them asap, or offer suggestions to disable
those features that are causing problems.
Hopefully by the time I post this, my test winform project that i F5'd
a few minutes ago will be compiled and in debug mode! What a great
opportunity to multi-task! F5, make a change, code, surf the web while
you wait to compile!
.
- References:
- Dear ms VS.NET 2005 development team
- From: jamesd
- Dear ms VS.NET 2005 development team
- Prev by Date: Dear ms VS.NET 2005 development team
- Next by Date: Re: vsnet 2005 - two questions
- Previous by thread: Dear ms VS.NET 2005 development team
- Next by thread: Re: Dear ms VS.NET 2005 development team
- Index(es):
Relevant Pages
|
