|
|
|
|
|
by stinos
4339 days ago
|
|
I've had more luck then. Strange they first say it will be fixed and then later say it won't be fixed anyway, I always had the impression they had their stuff together at Connect. Slowly of course but I guess that's what's to be expected because of the sheer size (this is not in their defense, at all, just my idea of why that is). Probably also spend tons of time looking at issues posted by people thinking Connect is a Q&A like StackOverFlow. Anyway for the 6 or so bugs I filed, all for the C++ compiler, the flow was 1. Submit bug report.
2. Get response like "we're looking into it"
3. Wait 2 to 5 months 4a. MS tech (or sometimes event Stephan T. Lavavej himself) posts a comment, "this will be fixed in the next release"
5. Bug report closed as fixed
6. Wait x time where x mainly depends on the point in time of the release cycle where 1 occurred. The later 1, the smaller x. You've gotta time those bugs to get them fixed quickly :P 4b: "won'tfix" / "by design" i.e. I got an explanation of what I did wrong, or otherwise why it happens 4c: "deferred" i.e. posted something that can be worked around and considered too minor of an issue to fix soon |
|