News for hackers. Stuff that matters.
Re:“Artery chokes after 70 copies of Visual Studio” by raxen on Thursday April 24, 2014 @09:03AM (#7639967)
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?
Re:“Artery chokes after 70 copies of Visual Studio” by ygra on Thursday April 24, 2014 @09:05AM (#7639979)
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” by petilon on Thursday April 24, 2014 @09:05AM (#7639982)
The Developer Division at Microsoft is responsible for both and this is their boilerplate response.
Re:“Artery chokes after 70 copies of Visual Studio” by Zenst on Thursday April 24, 2014 @09:23AM (#7640075)
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” by asveikau on Thursday April 24, 2014 @10:58AM (#7640671)
IIRC Internet Explorer used to overwrite the shell DLLs which contain a lot of random helpers and stuff that is not strictly shell related but tempting to make your application depend on. I remember this being a frequent source of "app not working, probably works on the developer's machine" type issues, especially in the time period where this was changing a lot.