“Today at TechEd, I announced Visual Studio 2013 and Team Foundation Server 2013 and many of the Application Lifecycle Management features that they include. […] I will not, in this post, be talking about many of the new VS 2013 features that are unrelated to the Application Lifecycle workflows. Stay tuned for more about the rest of the VS 2013 capabilities at the Build conference.”
So soon?
They just released 2012
Visual Studio 2013 was not released today, so a full year will have passed by the time it hits RTM.
All of Microsoft from Windows to Office are on a yearly release schedule now.
Wonder if they’ll change the somewhat annoying monochromatic icons back to the older more visually distinguished style
Which specific ones bother you? I find some of them *easier* than VS2010 because they’re a little more toned down. The colorful faux 3D of the old ones used to make it hard to know which icons are which.
The VS2012 RTM icons are much more colorful than the VS2012 Beta/RC releases.
From the screenshots they have gone to somewhat of an in-between between 2010 and 2012 … which I think is good.
Built in GIT support is pretty much a must after Github’s rise in popularity in the last few years.
The git support that they already have in VS 2012 update 2 also integrates with the Github for Windows client, so you can use both at the same time without them getting out of sync, and (IIRC) they even use the same git installation. It is definitely a welcome feature.
I haven’t used GIT extensively (just cloning some repos from github) and I haven’t really touched 2012 because I bloody well hate the colour scheme.
I can’t install it at work until we update parts of our core project because it relies on a version of Entity Manager that falls over with .NET 4.5 (even though they are supposed to be 100% API compatible).
Which colour scheme are you talking about? Last time I used git, it was still very fond of gray text on a black background…
If you are talking about the official “gitk” gui, now, I understand what you mean. It always amazes me how hideous Tk UIs can get.
Edited 2013-06-04 06:10 UTC
I was referring to Visual Studio.
OK, sorry for the temporary blindness :/
I already though that back in 1999, when we were using TCL/TK on our applications and remember the heavy discussions about using something else.
Glad to see some things never change.
Sure. Just like they fixed the missing Start menu in Windows 8.
Actually in VS2012 they listened to feedback and put “put energy into the icons”, not to my taste but they did listen.
If you look at the icons in the screenshot available you can see they aren’t monochromatic.
I feel like some of the stuff it does just makes developers lazy. I talk to a number of different developers at other companies that we work with, and it always seems like the ones who use VS are the ones least likely to know what’s really going on with complex issues. Or the answers to protocol questions are always given in terms of operations from within VS. Go to the X menu, Then J submenu, third tab should be Q, right click on it, then browse to File K and click okay. That should cause the Whodermunch to send a properly foiled Klershnopple.
Yeah there is quite a lot of developers that are like that, I work with a few but I think you find that a lot of it happens outside the Microsoft ecosystem as well (cough cough Java).
I used to work with a PHP developer that didn’t know hot to deal with a postback.
Some of the larger and older frameworks it supports fosters that mentality because nobody really understands how they work. It took me 6 months to get my head fully around WebForms, because it such a f–king weird web framework to work with especially after working with MVC framework like Django / RoR.
The other problem with Visual Studio it so damn large you don’t know if half the features exist in the first place.
Edited 2013-06-04 04:48 UTC
I thought it was supposed to be about coding and solving problems and not just about running some ide?
I don’t really see what you are getting at with that comment.
So instead of the promised quarterly updates for C++11 in Visual Studio 2012, we get to buy a new version. Great!
express compiler works well enough.
For playing around yes, but not when you require professional features.
Or frustratingly when you want to author a Portable Class Library. I can’t believe this isn’t in the Express SKU.
/me is still rocking VS6 \m/
Hope they fix the shitty C++ compiler in VS2012 before forcing another upgrade. Update 3 is supposedly scheduled for Q3 this year. Guess it won’t happen now.
For example, this bug should be fixed before VS2013:
https://bugreports.qt-project.org/browse/QTBUG-31248
It won’t happen, in case you don’t follow MSDN blogs,
http://blogs.msdn.com/b/bharry/archive/2013/05/08/some-thoughts-on-…
If you’re paying for Visual Studio, it is because you want to. There are a half dozen programs across Microsoft which includes VS as an added benefit.
I haven’t paid for VS since 2005.
In your part of the world there may be many possibilities to get it for nothing. Not where I am at.
However, half assing it doesn’t even begin to justify the upgrade mill MS is now pushing devs into. Upgrades also cost devs the effort and going through a new series of bugs. Things that were working in VS2010 borked in VS2012. How about the C++11 support they promised? What the point in rushing into a new VS?(probably more Metro goodness than before)
I am pretty pissed off with that one, specially since it was repeated multiple times by several Microsoft key persons.
So now they come and state update 3 is the last one, and it was mostly about UI and TFS related fixes?!
And when the head of Visual Studio development blogs about 2013, it mentions mostly ALM and devops tooling?!
http://blogs.msdn.com/b/somasegar/archive/2013/06/03/teched-2013.as…
I wonder if the going native stuff was driven by Steven Sinofsky and now that he is gone, company politics moved elsewhere.