F
Frank Rizzo
I am not able to grok, how after so many betas, CTPs, community
editions, flawless demos at MSDN shows, ms employees salivating at their
mouth over its goodness, etc... VS2005 can suck so hard. Is it just me,
or is VS2005 simply filled to the brink with all kinds of bugs? It's
integration with souce control simply sucks. I've seen instances where
it wants to add .PDB files to source control. And the file-based web
projects (web sites and web services) is simply an abberation. Who's
idea was it to drop a regular project type and go exclusively with the
file-based approach? All normal projects store their refs in the
..csproj file. Not file-based ones, they store them in the .sln file.
In a team environment, file-based projects are simply unworkable. God
forbid, someone has a test file in the directory. If you are not
careful, vs2005 will simply check the file into source control, thus
breaking everybody's build.
The web-based stuff is not the only problem. The Winforms. The
design-time experience gives a new meaning to the word "slow". Simply
try and drop a simple control onto a new form. Then click on it.
VS2005 simply hangs for a few seconds while it comes to its senses. And
god help you if you dropped a 3rd party grid on the form. Another cool
trick is to try and write code while your form is opened in another tab.
Guys, no offense, nothing personal and with a lot of respect to the job
before you, but while you still have customers, please, put out a
service pack and salvage your reputation built on great tools like
vs2003, vb1-vb6, vs6, etc...
Regards
editions, flawless demos at MSDN shows, ms employees salivating at their
mouth over its goodness, etc... VS2005 can suck so hard. Is it just me,
or is VS2005 simply filled to the brink with all kinds of bugs? It's
integration with souce control simply sucks. I've seen instances where
it wants to add .PDB files to source control. And the file-based web
projects (web sites and web services) is simply an abberation. Who's
idea was it to drop a regular project type and go exclusively with the
file-based approach? All normal projects store their refs in the
..csproj file. Not file-based ones, they store them in the .sln file.
In a team environment, file-based projects are simply unworkable. God
forbid, someone has a test file in the directory. If you are not
careful, vs2005 will simply check the file into source control, thus
breaking everybody's build.
The web-based stuff is not the only problem. The Winforms. The
design-time experience gives a new meaning to the word "slow". Simply
try and drop a simple control onto a new form. Then click on it.
VS2005 simply hangs for a few seconds while it comes to its senses. And
god help you if you dropped a 3rd party grid on the form. Another cool
trick is to try and write code while your form is opened in another tab.
Guys, no offense, nothing personal and with a lot of respect to the job
before you, but while you still have customers, please, put out a
service pack and salvage your reputation built on great tools like
vs2003, vb1-vb6, vs6, etc...
Regards