9 ms·
Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS re
by evo_9 13y ago
Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly.
This is not a Madden game, nobody is asking for yearly updates for Visual Studio.
- vyrotek 13y agoSeriously! My company has been keeping up with the latest stuff but I have hard time understanding what the justification was behind releasing a whole new Visual Studio version. Are there new features that won't be available in VS 2012? I guess we'll see at the Build conference.
- pjmlp 13y agoUpdate 3 was the last one. Maybe Microsoft is tight on money. :)
- trust-me 13y agoVS is not there to make money directly, but to sell MS platforms - Windows, SQL Server, etc. They give it away for free to students, startups and pretty much anybody who asks. The only reason all editions are not free is to not kill the other commercial Windows IDEs.
- pjmlp 13y agoReally? You don't have to pay for licenses I imagine.
- sixothree 13y agoI'm guessing adoption of 2012 is fairly low.
- snarfy 13y agoVS 2013 is for Windows 8.1.
- MartinCron 13y agonobody is asking for yearly updates for Visual Studio Ahem... I am. I would much rather have smaller more frequent updates to important tools than huge disruptive ones. Short feedback loops are a good thing.
- evo_9 13y agoFull new version or Service Packs? I agree with you but a Service Pack should suffice esp. right after you've release a full new version/update to a major product/tool like VS.
- MartinCron 13y agoThe full version vs. service pack distinction doesn't really matter to me.
- GFischer 13y agoIt makes a lot of difference to some PHB's, though. I'm pretty sure I can upgrade to a service pack. Changing versions, OTOH, probably requires approval from management.
- MartinCron 13y agoIt sounds like you have bigger problems than can be addressed by the hard-working people in Redmond.
- GFischer 13y agoUndoubtedly, you're correct :)
- dragonwriter 13y ago> I'm pretty sure I can upgrade to a service pack. Changing versions, OTOH, probably requires approval from management. Two things are apparent: 1) The problem you are addressing is a management problem in your organization, not a problem with Microsoft releasing a new version of VS. 2) You aren't the decision-making customer for Microsoft VS at your organization, so even the problem you had was with VS, it wouldn't necessarily be a problem MS would have much incentive to address.
- glhaynes 13y agoHow does it hurt, though? You say you're not running 2012 yet, so obviously you're not feeling forced to upgrade before you're ready. So why shouldn't they put out the latest bits when they've got them ready and we users can start using them when we're ready?
- evo_9 13y agoIf you've ever had to maintain a large, legacy .net app that has been around since 1.0 or even has some ASP 'classic' code in it, upgrading is a major nightmare. I know at least two shops right now 'stuck' on 2005 because various problems upgrading to 2008, let alone to 2012 or 2013 now. They are more likely to re-write the whole thing in Ruby at this point. I'm actually running 2012 personally, not such a big deal on that front, my side projects tend to be pretty manageable and not hugely large or sophisticated. But yeah, you have anything large and enterprise-y, the pain just amplifies each version you are behind.
- danbruc 13y agoYou can install several versions of Visual Studio side by side - keep an old version for maintaining legacy projects, use a new version for new projects.
- pjmlp 13y agoExcept you cannot have .NET 4.0 and 4.5 on the same machine, given the way 4.5 overwrites 4.0.
- deleted 13y ago[deleted]
- pjmlp 13y agoReality speaks otherwise, http://www.west-wind.com/weblog/posts/2012/Mar/13/NET-45-is-an-inplace-replacement-for-NET-40 http://www.west-wind.com/weblog/posts/2012/Mar/13/NET-45-is-... http://stackoverflow.com/questions/11458159/how-to-keep-net-4-0-behavior-if-net-4-5-is-installed http://stackoverflow.com/questions/11458159/how-to-keep-net-...
- samirahmed 13y agoI find this response almost shocking. Most of HN criticizes microsoft for slow releases cycles, slow change but the Visual Studio has clearly made progress for the better by addressing UserVoice requests, integrating Git etc. If your employer is to slow to keep updated, why should that slow MSFT down for you while the it is trying to reinvent itself, just catch up in 2015.
- Silhouette 13y agoMost of HN criticizes microsoft for slow releases cycles Just because it's trendy to bash MS for not releasing new browsers/IDEs/whatever every few weeks, that doesn't mean the vocal critics speak for all of us, nor even necessarily for the majority. I get paid to build stuff that works, and doing so requires stable foundations and reliable tools. Lately, I wish we had more Microsofts in the world paying attention to things like backward compatibility and long-term support, and fewer Googles and Mozillas and Apples who are quite happy to push out updates that break useful things that worked before. There was nothing wrong with releasing a major version when you had major new features, more frequent minor versions that introduced minor features in a compatible way, and point releases for urgent security issues or bug fixes that didn't change any intended behaviour at all. This approach has worked for a long time, and IMNSHO the recent regular, fixed schedules for updates regardless of actual changes aren't doing most people any favours, and the version-free, always-online, push-updates-whenever stuff is just a mess that causes far more trouble than it's worth.
- 3825 13y ago>Lately, I wish we had more Microsofts in the world paying attention to things like backward compatibility and long-term support, and fewer Googles and Mozillas and Apples who are quite happy to push out updates that break useful things that worked before. Did you mean forward compatibility?
- Silhouette 13y agoDid you mean forward compatibility? No, I really did mean backward compatibility. Specifically, I was thinking of the degree to which MS have supported even very old (by IT standards) APIs and file formats and protocols even in much newer (again by IT standards) systems over the years, and the lengths they have sometimes gone to in order to maintain that support despite the potentially breaking changes not even being their fault in many cases. However, I would also agree that they are better at forward compatibility than a lot of other major software developers today.
- Gazk 13y agoThere is a new SQL release, SQL Server 14.
- pjmlp 13y ago> This is not a Madden game, nobody is asking for yearly updates for Visual Studio. Sadly it seems to be the way it is going. Most likely driven by Windows 8.1.
- justncase80 13y agoI believe it is tied to the OS release: http://blogs.windows.com/windows/b/bloggingwindows/archive/2013/05/30/continuing-the-windows-8-vision-with-windows-8-1.aspx http://blogs.windows.com/windows/b/bloggingwindows/archive/2...
- deleted 13y ago[deleted]