More niggly issues with VS2005
-
I'll probably be adding to this list over the course of the day (I also want to point out that I'm not just being argumentative or overly critical, I just want the product to be what I need it to be): 1) In the Solution Explorer tab of the workspace window, "Source Files" really should be the first item in the tree (like it was in VS6). It makes more sense because I'm in the source files much more than the rest. 2) The Property Manager tab should be moved into the Solution Manager tree as the last tree item. 3) When you un-pin the workspace window, and then hover the mouse over the side-tabs, the workspace window shows up, but it doesn't account for the Error List window being displayed, and covers it up. 4) I turned off window animations, but there's still a speed penalty (in the form of a 1-2 second delay) involved in displaying un-pinned windows. It's almost like the IDE is still running through the code that animates the window, but just now displaying the visual changes until the window being rolled out says "okay, I'm finished rolling out". For completeness, I'll also mention that the side tabs on BOTH sides of the screen do this. The delay is also there when you move the mouse off the window that was rolled out. 5) The XP look and the non-adherance to user-specified system-wide window properties is still pissing me off. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
And here I am holding the pack of Team Suit CDs I managed to aquire for a test run. I insert CD1 in my drive, start the install, wait for 10 mins for it to initialise (P4 3.2Ghz, 768Ram), select components and the install begins... Really it will be quicker if I typed down those files manually using binary than for installer to copy them... And install reaches the first milestone called "Insert next CD". And I do it. And install still ask me to insert damned CD2. But it is already there. But install cannot see it. Cancel. And rollback starts...and ends in another 20 mins... Goodbye VS2005. It was nice knowing ya. -------------------------------- Human stupidity is infinite.
-
But none of the complaints in this thread have been about a particular language. I'm talking about usability and performance of the IDE here. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -- modified at 13:27 Sunday 11th December, 2005
John Simmons / outlaw programmer wrote:
I'm talking about usability and performance of the IDE here.
And I for one and glad you are posting. I like to make informed decisions when I lay out cash for a product, and your posts here are making me informed.
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ??? You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!
-
I agree MS and users of MS software need to be made aware but the posts I have seen here lately have not added anything new. Plus the posts are just lists of problems, not a discussion of them or the general problem. Anyway. I am watching the oil depot fires in England on telly. Loads more interesting :) regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
But you're still intrigued enough by the tedium to constantly check this thread and make responses. :) ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
But you're still intrigued enough by the tedium to constantly check this thread and make responses. :) ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Because it keeps popping into my inbox. I haven't said anything about the actual problems you had. regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Daniel Turini wrote:
It seems to me that, when you're talking about the "cost" of fixing bugs, are you talking about the cost for *you*, and when you're talking about the "cost" of not fixing bugs, you're talking about the cost for your customers, am I right?
Yes. It's always about balancing the cost of fixing the bug against how much not fixing it will cause your customer pain.
Daniel Turini wrote:
Since we're talking about a "cost" here, we're talking about US$, right? I can understand rough predictions of the cost of bug fixing, but how can you predict the cost of a bug being left on your code?
I think Joel explains it best[^] Michael CP Blog [^] Development Blog [^]
Joel sometimes writes good articles. But sometimes, he's shallow. As in this case. Do you know where this reasoning leads to? Ford Pinto[^]. To quote the article: "Ford waited eight years because its internal "cost-benefit analysis," which places a dollar value on human life, said it wasn't profitable to make the changes sooner." If people knew that Ford Pinto had a design problem that could cause it to explode, and that cost analysis decided that it was cheaper let people die on fire, do you think that so many people would buy it? IMHO, if you decide not to fix bugs you know before you release your software, you should clearly tell your customers which bugs are known. Then, see if your customers agree with this cost analysis. I don't see dead pixels anymore... Yes, even I am blogging now!
-
Just create a simple dialog. Put an "OK" button on it, and set the AcceptButton property to this button. Run the application. Show this Form from another one with "ShowDialog". Click "OK" and it won't close, because the DialogResult property wasn't properly set on the button. On VS 2003, this works. It took me 5 minutes to find this bug. Probably, someone would take another 5 minutes to fix it. I don't see dead pixels anymore... Yes, even I am blogging now!
As far as I know, setting the
CancelButtonproperty of a form sets theDialogResultfor that button toCancel. But setting theAcceptButtonproperty doesn't set theDialogResulttoOKbecause most of the time you don't always automatically close the dialog, but instead perform some validations, and probably won't close the dialog if they fail. -- LuisR
Luis Alonso Ramos Intelectix - Chihuahua, Mexico Not much here: My CP Blog!
The amount of sleep the average person needs is five more minutes. -- Vikram A Punathambekar, Aug. 11, 2005
-
Michael P Butler wrote:
Well, if they are like me then they probably weighed up the cost of fixing the bugs against the "cost" of not fixing them.
This is a sentence I see repeated again and again. Ok, so how do you measure the "cost" of fixing a bug? And how do you measure the "cost" of *not* fixing a bug? It seems to me that, when you're talking about the "cost" of fixing bugs, are you talking about the cost for *you*, and when you're talking about the "cost" of not fixing bugs, you're talking about the cost for your customers, am I right? Since we're talking about a "cost" here, we're talking about US$, right? I can understand rough predictions of the cost of bug fixing, but how can you predict the cost of a bug being left on your code? I don't see dead pixels anymore... Yes, even I am blogging now!
Here's another very good article on this subject: My Life as Code Economist[^] by Eric Sink, from SourceGear. -- LuisR
Luis Alonso Ramos Intelectix - Chihuahua, Mexico Not much here: My CP Blog!
The amount of sleep the average person needs is five more minutes. -- Vikram A Punathambekar, Aug. 11, 2005
-
I'll probably be adding to this list over the course of the day (I also want to point out that I'm not just being argumentative or overly critical, I just want the product to be what I need it to be): 1) In the Solution Explorer tab of the workspace window, "Source Files" really should be the first item in the tree (like it was in VS6). It makes more sense because I'm in the source files much more than the rest. 2) The Property Manager tab should be moved into the Solution Manager tree as the last tree item. 3) When you un-pin the workspace window, and then hover the mouse over the side-tabs, the workspace window shows up, but it doesn't account for the Error List window being displayed, and covers it up. 4) I turned off window animations, but there's still a speed penalty (in the form of a 1-2 second delay) involved in displaying un-pinned windows. It's almost like the IDE is still running through the code that animates the window, but just now displaying the visual changes until the window being rolled out says "okay, I'm finished rolling out". For completeness, I'll also mention that the side tabs on BOTH sides of the screen do this. The delay is also there when you move the mouse off the window that was rolled out. 5) The XP look and the non-adherance to user-specified system-wide window properties is still pissing me off. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
This has to be one of the longest threads I've seen on CP. If no pretty close. I wonder w hat the thread count is on the longest conversation on CP is. Thanks, John
-
Joel sometimes writes good articles. But sometimes, he's shallow. As in this case. Do you know where this reasoning leads to? Ford Pinto[^]. To quote the article: "Ford waited eight years because its internal "cost-benefit analysis," which places a dollar value on human life, said it wasn't profitable to make the changes sooner." If people knew that Ford Pinto had a design problem that could cause it to explode, and that cost analysis decided that it was cheaper let people die on fire, do you think that so many people would buy it? IMHO, if you decide not to fix bugs you know before you release your software, you should clearly tell your customers which bugs are known. Then, see if your customers agree with this cost analysis. I don't see dead pixels anymore... Yes, even I am blogging now!
Daniel Turini wrote:
Joel sometimes writes good articles. But sometimes, he's shallow. As in this case. Do you know where this reasoning leads to? ... Then, see if your customers agree with this cost analysis.
I'm sorry, but I think Joel was right on this one. Your example looks great, but it's extreme and it doesn't apply here. The cost-benefit analysis should be done by any supplier, and his article explains how he did it in his case. The only trouble is that it has to be done properly. Ford obviously didn't. Because, no matter what decision do you reach after the analysis, some people will be less than thrilled. you just have to make sure you make unhappy fewer people and/or less influential one. I'm not very excited when I get the wrong end of such a decision myself, but that is not because the idea of the cost-benefit is faulty. Maybe someone applied it badly or I'm just too small a fry. OGR
-
Whats tedious are people who just blindly accept that everyone should remain calm while Microsoft ruins our programming careers. I think the people who make it obvious that Visual Studio 2005 is less than satisfactory, help the rest of the public make that fateful decision of whether to fork over the cash for another half baked tool. I've read some of Marc's blog but he's not the only voice in our industry. Let him speak his two cents. I thoroughly enjoy the feedback, good and bad, people have for this product. It points me too all the issues and cool features. My code is slowly becoming deprecated but it is so non-portable because it utilized some of Microsoft's previous "time saving" technologies. I've backed myself in a corner cause I have two choices now, buy something that doesn't work and will force me to spend time on workarounds instead of churning out code, or I can make the effort to port my code. Either, way does not sound attractive. Thanks Microsoft....Let the man rant. They deserve the bad press!
bob16972 wrote:
Whats tedious are people who just blindly accept that everyone should remain calm while Microsoft ruins our programming careers.
MS ruining my/your career? You must be joking! The worse their products are, the harder they are to use. The easier it is to make the difference between a good developer and an also-run. It is crappy products that make you an expert, you don't get any bonus points for being able to use the remote of your TV set. Apart from that, I fully agree with you. OGR
-
bob16972 wrote:
Whats tedious are people who just blindly accept that everyone should remain calm while Microsoft ruins our programming careers.
MS ruining my/your career? You must be joking! The worse their products are, the harder they are to use. The easier it is to make the difference between a good developer and an also-run. It is crappy products that make you an expert, you don't get any bonus points for being able to use the remote of your TV set. Apart from that, I fully agree with you. OGR
-
This has to be one of the longest threads I've seen on CP. If no pretty close. I wonder w hat the thread count is on the longest conversation on CP is. Thanks, John
This one probably is around 50-60 posts. I remember seeing one at 116 posts. -- LuisR
Luis Alonso Ramos Intelectix - Chihuahua, Mexico Not much here: My CP Blog!
The amount of sleep the average person needs is five more minutes. -- Vikram A Punathambekar, Aug. 11, 2005
-
I'll probably be adding to this list over the course of the day (I also want to point out that I'm not just being argumentative or overly critical, I just want the product to be what I need it to be): 1) In the Solution Explorer tab of the workspace window, "Source Files" really should be the first item in the tree (like it was in VS6). It makes more sense because I'm in the source files much more than the rest. 2) The Property Manager tab should be moved into the Solution Manager tree as the last tree item. 3) When you un-pin the workspace window, and then hover the mouse over the side-tabs, the workspace window shows up, but it doesn't account for the Error List window being displayed, and covers it up. 4) I turned off window animations, but there's still a speed penalty (in the form of a 1-2 second delay) involved in displaying un-pinned windows. It's almost like the IDE is still running through the code that animates the window, but just now displaying the visual changes until the window being rolled out says "okay, I'm finished rolling out". For completeness, I'll also mention that the side tabs on BOTH sides of the screen do this. The delay is also there when you move the mouse off the window that was rolled out. 5) The XP look and the non-adherance to user-specified system-wide window properties is still pissing me off. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
John Simmons / outlaw programmer wrote:
"Source Files" really should be the first item in the tree
..ideally this would be a configurable option (a lot of people start off with the designer. BTW you should be able to use shortcut key F7 to open source straight away.
John Simmons / outlaw programmer wrote:
- The Property Manager tab should be moved into the Solution Manager tree as the last tree item.
Not sure I understand. If you're changing properties for an item in the sol/exp. you need to keep that item selected while you edit it's properties.
-
No offense, but I'm not sure I get what your saying. I reread your post three times and the thread and I guess I'm missing something here. Please advise...
Translation: "What doesn't kill you makes you stronger." My opionion: Rubbish. Translation: "Rubbish." Being forced to use crappy tools to do your job doesn't make you a better programmer. It makes you a victim of circumstances. Translation: "Rubbish." ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
John Simmons / outlaw programmer wrote:
"Source Files" really should be the first item in the tree
..ideally this would be a configurable option (a lot of people start off with the designer. BTW you should be able to use shortcut key F7 to open source straight away.
John Simmons / outlaw programmer wrote:
- The Property Manager tab should be moved into the Solution Manager tree as the last tree item.
Not sure I understand. If you're changing properties for an item in the sol/exp. you need to keep that item selected while you edit it's properties.
Not sure I understand. If you're changing properties for an item in the sol/exp. you need to keep that item selected while you edit it's properties. The property manager tab is for the solution, not for individual files. It should be placed where it makes more sense. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
This has to be one of the longest threads I've seen on CP. If no pretty close. I wonder w hat the thread count is on the longest conversation on CP is. Thanks, John
I've seen threads with more than 200 posts. Don't worry, I'll be starting another thread VS2005 shortly. :) ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
I'll probably be adding to this list over the course of the day (I also want to point out that I'm not just being argumentative or overly critical, I just want the product to be what I need it to be): 1) In the Solution Explorer tab of the workspace window, "Source Files" really should be the first item in the tree (like it was in VS6). It makes more sense because I'm in the source files much more than the rest. 2) The Property Manager tab should be moved into the Solution Manager tree as the last tree item. 3) When you un-pin the workspace window, and then hover the mouse over the side-tabs, the workspace window shows up, but it doesn't account for the Error List window being displayed, and covers it up. 4) I turned off window animations, but there's still a speed penalty (in the form of a 1-2 second delay) involved in displaying un-pinned windows. It's almost like the IDE is still running through the code that animates the window, but just now displaying the visual changes until the window being rolled out says "okay, I'm finished rolling out". For completeness, I'll also mention that the side tabs on BOTH sides of the screen do this. The delay is also there when you move the mouse off the window that was rolled out. 5) The XP look and the non-adherance to user-specified system-wide window properties is still pissing me off. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Another thing that really gets me is the delay in the property window when I select a different control. It takes a good 1-2 seconds for the name of the control to change. This really irks me because sometimes I quickly go to change a property, and it's still on the previous control. I know it's not my computer, because the rest of the app is pretty speedy. BAH! Brigg Thorp Senior Software Engineer Timex Corporation