Hacker News new | ask | show | jobs
by jheriko 4436 days ago
hehe.... i wonder if they will fix it or simply accuse you of being an idiot several times over before reading the bug report and realising its genuine. :P

what i find much more interesting than this kind of bug though is that there are several possible ways to expose vs bugs with one step after making a new project in the current version...

1 comments

The issue has already been closed as Fixed.
Based on my experience with connect that doesn't mean it was fixed in the product version you reported it against or any future version.
They mention future version of 2013. So its gone to their bug reports database, to be prioritized rather than is fixed.
From the description of the resolution reasons, that'd be "Deferred".
I'd imagine deferred, is less "pre-grooming" as "nice-to-have-some-time". But I dont work for MS.