Microsoft (Dis)Connect Feedback
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I've gotten that too. Seems like a tactful way of saying:
Microsoft is really thinking:
We already suckered you all into buying our product. We're not going to waste time fixing something you already find workable. Did we mention you're a bunch of suckers, suckers?
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Where do I vote? I can't say I've found the issues you're talking about, but there are enough issues with the VS2010 editor (as good as I personally believe it to be) that a statement like ; "Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. " Hold on, I bought VS2008 and when 2010 came out I paid the extra $300 to upgrade to that, and statements like, "these annoying issues that make the editor a difficult experience aren't important enough" make me want to vote if I can to get them to look at it. If they can't be bothered to fix their editor, why should I spend money on the next version of VS which will contain similar annoyances.
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I am no longer surprised by that kind of response from MS: I posted on a similar note last September. http://www.codeproject.com/Messages/3592664/Why-Microsoft-cant-fix-bugs-official.aspx[^]
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997These are the same people who I approached with a question years ago. Their answer... "That isn't possible". When I simply had to find a solution, I figured it out for myself and then forwarded my solution to them. Their response again was, "That can't possibly work." As far as I know my solution is still executing in production code. That was 8 years ago.
I wasn't, now I am, then I won't be anymore.
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997At least they didn't tell you that an issue which crashes the IDE is a feature.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Where do I vote? I can't say I've found the issues you're talking about, but there are enough issues with the VS2010 editor (as good as I personally believe it to be) that a statement like ; "Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. " Hold on, I bought VS2008 and when 2010 came out I paid the extra $300 to upgrade to that, and statements like, "these annoying issues that make the editor a difficult experience aren't important enough" make me want to vote if I can to get them to look at it. If they can't be bothered to fix their editor, why should I spend money on the next version of VS which will contain similar annoyances.
http://connect.microsoft.com/VisualStudio[^] Issue # is 645507
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
At least they didn't tell you that an issue which crashes the IDE is a feature.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
At least they didn't tell you that an issue which crashes the IDE is a feature.
but it is, just check the requirements spec: Visual studio requirements specification ... CG1 Visual studio shall produce a random crash when user is Christian Graus. CG2 Visual studio shall produce a random error when user is Christian Graus. ... CG99 All new bugs shall be classified as features if reported by Christian Graus and requirements to maintain them in future versions shall be added. ... :doh:
3x12=36 2x12=24 1x12=12 0x12=18
-
http://connect.microsoft.com/VisualStudio[^] Issue # is 645507
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997My vote is there. Any other issues you want voting for, I'll add mine.
-
I've gotten that too. Seems like a tactful way of saying:
Microsoft is really thinking:
We already suckered you all into buying our product. We're not going to waste time fixing something you already find workable. Did we mention you're a bunch of suckers, suckers?
Can't believe I missed another chance to tweak the Bad Word filter this morning...
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Can't believe I missed another chance to tweak the Bad Word filter this morning...
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
You've for_gotten_ again? Frak.
-
You've for_gotten_ again? Frak.
Invalid emphasis. The word "forgotten" is perfectly fine as far as Chris is concerned. It's "gotten" that Chris insists is not a word. Let's try to keep things on an even keel here. And by the way, the correct emphasis to be placed on the word in question is bold + italics + big, like this. If you don't do it that way, and if it doesn't look like it's otherwise part of normal conversation, it can't be counted as being properly used within the context of CodeProject.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Where do I vote? I can't say I've found the issues you're talking about, but there are enough issues with the VS2010 editor (as good as I personally believe it to be) that a statement like ; "Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. " Hold on, I bought VS2008 and when 2010 came out I paid the extra $300 to upgrade to that, and statements like, "these annoying issues that make the editor a difficult experience aren't important enough" make me want to vote if I can to get them to look at it. If they can't be bothered to fix their editor, why should I spend money on the next version of VS which will contain similar annoyances.
yah ... i didn't spend money on it as it sucked then and it looks to still suck now :)
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
These problems "don't meet the requirements" to be fixed in a service pack,
... because there are so many, many more serious flaws that need fixing.
___________________________________________ .\\axxx (That's an 'M')
-
What I submitted: I've encountered several annoying syntax highlighting issues since starting to use VS2010: 0) Text Editor String background color applied to leading white space in XAML files. 1) Cursor doesn't change to contrasting color when placed on a dark background color. 2) Hyperlink strings in CS code are not displayed the specified string foreground color, but DO use the specified string background color. 3) Annoying white space gap between lines in multi-line comments. How They Responded: Thank you for reporting these issues. It does appears that XAML strings are not being classified incorrectly. I have routed the feedback to the team that works on the XAML editing experience. I agree that it would be better to have the caret contrast with the background that it is on rather than the Editor background colour. Our colorizer for URLs is more specific than strings and so it has a higher priority, you can change the colour for it by choosing the URL Hyperlink option. I also agree that it the syntax highlighting should also extend vertically so that you do not see the banding that you've reported. Unfortunately, these changes do not meet our requirements for being addressed in the Service Pack but we will keep these in mind as we are working on the next version of Visual Studio. If other customers see this issue and want to help us prioritize it, please use the voting buttons. Thanks! -Sean Laberee VS Pro Team ------------- I expected this kind of response. These problems "don't meet the requirements" to be fixed in a service pack, and if they're THAT minor, trying to convince me that they'll be addressed in a major release is beyond absurd.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997You should be impressed that you got a response. The couple of times I've posted an issue on Microsoft Connect the issues were closed without comment or explanation.
Software Zen:
delete this;
