|
|
It sometimes does
One of my major complaints about C++ source code regions is supposedly fixed in VS2010
|
|
|
|
|
peterchen wrote: complaints about C++ source code regions is supposedly fixed in VS2010
That is a big frustration of mine. I mean the fix is in a new version..
John
|
|
|
|
|
No.
Why should they? If they sit on them for a few months they can discontinue the product and force us a buy a new set of bugs to remain "current."
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
In my experience bugs reported through "connect" are rarely worked on.
If you are able to report them through the telephone technical support service that is available to partners the success rate is much greater. Although telephone tech support is a paid for service any report confirmed as a bug will be handled free of charge.
The response will be proportional to the "criticality" of the problem so I would only recommend reporting serious problems that have no workaround through this route.
|
|
|
|
|
Andrew Wiles wrote: through "connect" are rarely worked on
Interesting.
Andrew Wiles wrote: have no workaround
Yeah, I've been dubious about providing workarounds that I've found in case they think that they no longer need to bother. I think in future I'll keep that part to myself, or put in my CP blog that I've never used.
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
|
|
|
|
|
I have had 3 of my Connect reports accepted ad bugs and fixed.
Dave.
|
|
|
|
|
During the beta of VS 2005 I had a number of bugs fixed and closed (and I was really impressed with the service), but since then they have been mostly closing them saying, as you said, they don't have time. However, a few of my bugs have still been marked as fixed, or suggestions taken on board for future versions.
Uusually, if all I get is the stock response (as you mention above) I post a comment complaining about a lack of individual feedback, and mark the bug re-opened. Someone usually looks at it again, and then posts a reply comment stating it's a good idea/bad idea, or it's by design/not by design or explaining why it's hard to fix. Sometimes they say they'll defintely look at it for the next release. At least that makes me feel a little better.
Also, I contacted the connect team once to ask if anyone reviewed or was notified of comments posted to 'closed' tasks, and apparently it's best to re-open them if you're posting a comment you want a response to, otherwise it's likely to go ignored.
In general, I think the best time to get a bug fixed is during a beta, and you're far more likely to get it fixed if it's a 'new bug' rather than one that has been around for several prior versions. Also, I wouldn't expect any suggestion to make it into the release they are currently working on, i.e if you made one within the last 12 months you shouldn't expect to see it before whatever comes after VS 2010, if it ever gets done at all.
|
|
|
|
|
Of course MS cares!
Have a look at this video:
WSYP Project[^]
Regards,
Ricardo Corona
|
|
|
|
|
|
If it's good enough for Weven, it's good enough for Visual Stupido...
"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 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
As if Visual Studio wasn't slow enough already.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
If you don't ask questions the answers won't stand in your way.
Most of this sig is for Google, not ego.
|
|
|
|
|
but but but... it will be shineeeeeeeeeeeeeeeeeee.........
[edit]
but do you think this will let them add current line highlight?
[/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
|
|
|
|
|
l a u r e n wrote: but do you think this will let them add current line highlight?
From what i've heard, that's the idea. Well, not that specifically, but in terms of making it easier to add graphical enhancements to the editor without the horrible, fragile hacks necessary to do so in previous versions of VS.
|
|
|
|
|
l a u r e n wrote: but do you think this will let them add current line highlight?
Isn't that what that funny blinking vertical bar thingie is for?
"It's so simple to be wise. Just think of something stupid to say and then don't say it."
-Sam Levenson
|
|
|
|
|
ummmmmmmmmmmm no ... i mean the whole line background color ... you know ... like every other text editor on the planet has
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
|
|
|
|
|
"It's so simple to be wise. Just think of something stupid to say and then don't say it."
-Sam Levenson
|
|
|
|
|
I don't like shiny. I like medium grey, menues, and nice sharp pointy corners.
|
|
|
|
|
+1 wpf apps take a little bit longer to load !
|
|
|
|
|
Jim Crafton wrote: Can anyone confirm or deny this atrocity?
Confirmed[^]. It is used for the new code editor. Not that I would use VS for code editing anyway
|
|
|
|
|
What about the rest of the IDE? The few things I read seemed to imply that the whole shell was going the way of WPF.
|
|
|
|
|
Well it already uses Windows Forms - so, I don't think WPF would make it slower in particular. In fact it may get faster with a good fast video card.
|
|
|
|
|
Nishant Sivakumar wrote: Well it already uses Windows Forms
Not for the code editor, AFAIK.
|
|
|
|
|
Nemanja Trifunovic wrote: Not for the code editor, AFAIK.
True.
|
|
|
|
|
Great. You need a DX12-compatible video card with a billion fracking shaders and pixel pipelines to get the File Open dialog to display. Just what we need...
"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 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|