But this obsessive need to be on-message and then not reply to criticism until the next carefully stage-managed event was a hallmark of the Sinofsky and Ballmer days, and now we have an actual developer back in charge of the company again, perhaps it will change. I do think they are a bit crap at communicating why things change and good at getting defensive / shutting up when challenged. I don’t doubt there are plenty of people in Microsoft’s marketing department who would love to do just that – ditto Google’s and Apple’s – but I don’t think the VS team is that way inclined. In these cynical times, any change you don’t happen to like gets portrayed as an attempt to grab your data or spy on you or hold you to ransom for more money.
Visual Studio from MSDN has been pre-keyed for ever, no reason we should expect that to change without being told.
I agree that Microsoft should have actually communicated this properly, though. As David mentions above, you can get the proper key from your MSDN subscription and make it go away. I assume the change was to allow you to sign in on VS2013 on any old machine and be able to use it, and hence the online validation. In these days of increased data collection sensitivity, I didn’t expect this move from a company claiming to be different from the competition. Not only because of the sign-in required every 30 days (and the need to be online, as you’ve found out) but also due to the administrative overhead and privacy implications. Needless to say, we’re reluctant to move from VS 2012 which we’re currently using, to VS 2013. Oh, and implicitly, who they work for of course, as we need to “associate” these accounts with our Microsoft partner account, and keep managing these associations. Which means that all of our developers need to get a Microsoft account, and get forced into providing our “partner” with their first and last names, gender, e-mail and zip code. (Looks like the same sort of license that you’ve got)
The “sign in into Visual Studio” which is optional if you’ve got a regular license, isn’t for us. Starting with Visual Studio 2013, these are now treated as 30 day trial licenses. As part of the “partner” deal, we are entitled to 35 Visual Studio licenses. I work for an ISV and long-time Gold Certified Microsoft partner.
0 kommentar(er)
