21–30 of 99 posts
Earlier quoted context omitted.
I run multiple instances of vs.net and don't reboot every week, In my case, I'm cycling through at least 10 instances a day. This bug report is actually interesting (to me).
Yes, but do you shut them down ungracefully? Do you expect to read interesting bug reports on HN?
Earlier quoted context omitted.
I run multiple instances of vs.net and don't reboot every week, In my case, I'm cycling through at least 10 instances a day. This bug report is actually interesting (to me).
Yes, but do you shut them down ungracefully? Do you expect to read interesting bug reports on HN?
Earlier quoted context omitted.
One main project (open all day) and small projects throughout the week/month with a machine never shut down? I can see that happening easily at web agencies and the like.
Any more than 5 instances of VS running on one machine gives me pause. I can't imagine going into double-digits, let alone 50+. I can see 70 files or projects open, but not in VS. EDIT: Ah, seems I skipped the part where the additional instances are closed.
Earlier quoted context omitted.
I run multiple instances of vs.net and don't reboot every week, In my case, I'm cycling through at least 10 instances a day. This bug report is actually interesting (to me).
Yes, but do you shut them down ungracefully? Do you expect to read interesting bug reports on HN?
I agree that vs.net is not really pertinent to the core 'hacker' audience here, but this bug report is actually relevant to me, and I didn't get it from my MS-oriented feeds.
I should read HN's FAQ, but aren't articles making it to the front page by being upvoted from new?
Is there a repository somewhere of really great bug reports like this? Something along the lines of "commits from last night".
For this bug, it would be a very small or non-existent bounty since this use case affects almost no one, but what if someone found a major bug that was not a security issue, and worked out the cause and fix, as was done in this case? Is that so much less valuable than a security issue?
Not that this is a major bug, but it makes me wonder why a bug report of this detailed nature (basically doing the debugging for Microsoft engineers) shouldn't be eligible for a bounty, just as exposed security flaws are. For this bug, it would be a very small or non-existent bounty since this use case affects almost no one, but what if someone found a major bug that was not a security issue, and worked out the cause…
If you don't report it, then there is slim chance of the bug being fixed.
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...
The issue has already been closed as Fixed.