Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

“Artery chokes after 70 copies of Visual Studio”

connect.microsoft.com

Post reply on HN
Print view View original

11–20 of 99 posts

Re: “Artery chokes after 70 copies of Visual Studio”

#12

Post by ygra »

raxen wrote: post #11
Serow225 wrote: post #9

Now that's how bug reports should be written!

Agreed but I was confused by the MS response of "Thank you for submitting feedback on Visual Studio and .NET Framework." It seems like the bug is in VS and not .NET. Are they that interweaved these days?

The bug report frontend is for both. The Thank you is just an automated response that it was seen. Generally, lots of the official replies on Connect seem to be either text building blocks or canned responses. Not terribly surprising, either, I might add.

Re: “Artery chokes after 70 copies of Visual Studio”

#13

Post by petilon »

raxen wrote: post #11
Serow225 wrote: post #9

Now that's how bug reports should be written!

Agreed but I was confused by the MS response of "Thank you for submitting feedback on Visual Studio and .NET Framework." It seems like the bug is in VS and not .NET. Are they that interweaved these days?

The Developer Division at Microsoft is responsible for both and this is their boilerplate response.

Re: “Artery chokes after 70 copies of Visual Studio”

#14

Post by ygra »

jheriko wrote: post #10

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.

Re: “Artery chokes after 70 copies of Visual Studio”

#15

Post by ygra »

prawks wrote: post #6
masklinn wrote: post #5

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.

My cat once managed to launch 167 instances ;-)

Re: “Artery chokes after 70 copies of Visual Studio”

#16

Post by Zenst »

raxen wrote: post #11
Serow225 wrote: post #9

Now that's how bug reports should be written!

Agreed but I was confused by the MS response of "Thank you for submitting feedback on Visual Studio and .NET Framework." It seems like the bug is in VS and not .NET. Are they that interweaved these days?

in 1998 I was working with VS and had a bug with OCX and was told that the bug was due to VS not working with the current IE version as well in places and was fixed in the new release of VS due out.

So I'd say very interweaved if history has its design legacy mantra.

Re: “Artery chokes after 70 copies of Visual Studio”

#17

Post by nraynaud »

Serow225 wrote: post #9

Now that's how bug reports should be written!

I don't think you can always expect your users to do the reduction and the debugging for you, they pay you for a bug free product. In this case it's a developer-centric product, so I guess the bug reports are more geeky, but customers are not here to serve the developers.

Re: “Artery chokes after 70 copies of Visual Studio”

#19

Post by yread »

QuadDamaged wrote: post #18
yread wrote: post #3

Why is this interesting?

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?

Post reply on HN