2 Comments

  • Please don't overreact about stuff like that man. That kinda stuff really looks bad when newbies come in looking for information. Bugs are bound to come up just like anything else. There's no need to overblow it.

  • To me, this kind of stuff is a big deal. Customer's can be extremely skittish about upgrading production machines, and this kind of stuff fuels that fire. I mean, we're not talking about some obscure feature here - we're talking about something as basic as performance monitoring. And we're not talking about something that worked on 1.0 that's broken on 1.1 - we're talking about something still running on 1.0 that breaks merely because of the presence of 1.1. Avoiding these problems is the whole reason for side-by-side, so it's not good that it's broken right out of the gate. Credit to Microsoft for providing a fix quickly, but it's still troubling. It also kind of sucks that a) you have to call MS to get the fix, and b) the fix is for 1.0, not 1.1.

Comments have been disabled for this content.