Express for Desktop allows for non-metro development in Visual Studio 2012
arstechnica.com
arstechnica.com
I don't expect much success with Windows 8, due to a combination of there being a lot of genuine rough edges and gaps in the new environment and in how it relates to the desktop, most people not really feeling a need for a new version of Windows right now anyway, and people's normal resistance to change. However, they'll probably continue to improve the Metro stuff in future Windows versions, and eventually it will just become another boring established part of Windows that everyone takes for granted. At which point it won't be the new shiny anymore and balance will be restored.
http://msdn.microsoft.com/en-us/windows/hardware/hh852363.as...
As long as they continue to ship a C++ compiler freely, I'll be happy.
It would be strange to make a non-metro version of Visual Studio have those menus with that rational, but it would also be weird to have two versions of Visual Studio, one with capped menus and the other without.
The all-caps menus are part of the Metro "design language," which is related to but separate from actual Metro applications that run within the new non-desktop interface. Additionally, it's already been revealed that there will be a setting to return the menus to regular capitalization, and it can be done in the beta via a registry key.
Edit: As drivebyacct2 points out below I am wrong, it HAS in fact been officially stated. I don't see any attribution on the blog entry, but I suspect I know who wrote it and it is an official Microsoft blog, so that is a public announcement. Done and done.
>That said, we will enable you to customize the casing, and we are exploring options for how to expose that choice. We will post again once we’ve settled on a final approach to be available in RTM.
In my experience such interaction generally takes the form (some hyperbole for humorous effect):
Customer: You are incompetent because you made decision X.
Me: We made decision X for the following reasons (enumerate things that weighed in on the decision).
Customer: You are worse than Hitler and need to die.
A counter-example is how ScottGu handles situations like this -- or used to, nowadays he doesn't seem to have that much free time. When one posts about a problem on his blog he gets personally involved and assigns somebody to get it fixed. On the other side, one thousand people ask for the same thing and they're being ignored. Do you see my point?
The problem is the people they are 'yelling louder' at are not the people making the decisions, they are simply the ones that have to/volunteer to face the mob. I try and be civil in my feedback for products I use even if I am pissed off because I know there is a human being at the other end and they are more than likely operating under similar constraints/deadlines/rules as everyone else in the world. Sometimes I disagree with their decisions, sometimes violently, but I try to approach the conversation from the mindset that they aren't simply doing it to annoy me, because they aren't.
>Claiming to paying attention to feedback when clearly not doing so is also quite frustrating.
Not sure how we could be considered to be ignoring people. Have you seen this announcement? Have you seen the massive UX changes due to Beta feedback? The only thing I can think of is the ALL CAPS issue, but that actually came in RC itself, and as someone else pointed out in the GP of this thread, that is also announced as being something that users will be able to tweak.
>A counter-example is how ScottGu handles situations like this -- or used to, nowadays he doesn't seem to have that much free time.
ScottGu is a VP now, he likely doesn't involve himself personally in many issues like that anymore as it doesn't scale and his time is more valuably spent in other pursuits.
>On the other side, one thousand people ask for the same thing and they're being ignored. Do you see my point?
I would if people were actually being ignored, I don't see anything in any recent announcement that would indicate that. Care to point out an issue with lots of feedback that is being ignored? And to be clear I don't consider "ignored" == "not doing what I want them to". Feedback can be given, even at large volume, and not result in a change of course. If the people making the decisions feel, even in the light of the feedback, that their course is correct that is their decision to make. Ignoring would be simply not even addressing the feedback at all and just blindly going about your planned course as if the feedback didn't exist.
If I think to the major feedback points I recall they were
Feedback: Don't like only being able to make Metro apps with Express.
Conclusion: See the post this thread is located in.
Feedback: Hate (dislike strongly) the UX in Beta.
Conclusion: See the RC release.
Feedback: Hate the ALL CAPS menu in RC.
Conclusion: See blog post where it was said officially that there will be a way to tweak this (not sure what that way will be, but it will be present).
Feedback: Hate that I can't build things in C++ that target XP using 2012.
Conclusion: Still sad panda (I have no hand in that matter though so I can't speak with any intelligence on it).
lol. I apparently need to come give the VS team a brief on the VS team decisions. They've reacted to that crticism as well and are going to release an Express SKU with Desktop support.
http://blogs.msdn.com/b/visualstudio/archive/2012/06/08/visu...
http://connect.microsoft.com/VisualStudio/feedback/details/6...
When the original beta was introduced it was not a "hey guys, what do you think of the new UI" type of announcement. It was more of a "this is the new UI, it adheres to the latest and greatest design trends, is better, prettier, more 'energetic'; you will love it!" People felt patronized so they gave their feedback in droves.
This later set the tone that the only way they're going to listen is if we bury them in feedback. Of course this is unfortunate as good feedback was probably lost in the noise.
Also, there's tons of feedback that is being ignored: http://visualstudio.uservoice.com/forums/121579-visual-studi... A simple "maybe" or "won't do because X" would go a long way.
Here are the top requests:
>Change All CAPS Menu in VS RC to VS Beta format File Edit Instead of FILE EDIT
Already beat to death in this thread, and there has been a public blog post, hardly ignored.
>Add some color to Visual Studio 11
See RC release. Also see the comments section where there are posts from VS team members, so ignored is not quite the right word. I find a certain irony in the comments asking for the 2010 theme back, when we released 2010 there was a large amount of feedback of people that hated 2010 and wanted 2008 back.
>Make .NET 4.5 work on any OS that supports 4.0
See my comment about this not being resolved. It certainly isn't being ignored though.
>Visual Studio 11 Express on Windows 7 and the ability to write non Metro C++ applications in it.
Hmmm yeah something about that link I posted to start this whole thread.
>change the new 2012 RC bowtie icon back to the smooth style
Well, suggestion I guess. I doubt that will happen (branding changes are generally made by marketing). There is no comment there so this is the first one I think you could say has 'been ignored'.
>Leave VS 2010 theme (and the theme editor extension) as an option
Well okay, unlikely to happen, re-theming VS is not a small undertaking (we have multiple UI technologies in play, it isn't as simple as declaring a CSS file) and supporting 3 (dark + light + 2010) would be a large undertaking. As for the theme editor, it is still there, in fact it was written by the guy in the office next to me. I don't think it is 'going anywhere' and I would be shocked beyond belief if it didn't support 2012.
There are many more, I guarantee you there are PMs that have read every single one of those (fun times!). Not all have comments, so I guess if that is where you are going with 'being ignored' then it is accurate, but it is a bit of a stretch considering the most popular ones have all been addressed in one form or another.
I get what you are saying about the psychology, it is funny this all started because I made a comment on how I don't read the comments because, in my experience, they are fairly vituperative. That is me, I am not here representing as an official spokesman for VS or Microsoft so please don't apply that label to me as I have gone out of my way to make it clear I am NOT such a role. If you think no one is reading them, well I doubt I could convince you otherwise, though it is clearly not true.
Maybe not for long, there is a work in progress: http://tedwvc.wordpress.com/2012/03/11/how-to-get-visual-c-2...
That was my understanding. I guess I expressed myself poorly. I was wondering why a piece of software that is apparently explicitly for 'Desktop' (as in creating things for it) would sacrifice sensibility for the sake of any Metro concepts.
I don't know, the entirety of it is weird to me, so maybe this makes more sense to somebody who understands the reasoning behind everything else about windows 8.
I will however just leave this here:
http://www.richard-banks.org/2012/06/how-to-prevent-visual-s....
This is of course not officially supported and my being a VS team member does not imply a contract for this registry key to exist for all time or on any specific SKU.
Another thing I can't wrap my mind around is how can it be possible to have one thousand of your customers yelling at you they don't like something -- that can be easily changed -- and have the management respond with "Oh well, we're still going to do what we want. What ya gonna do about it?!"
In my experience it is the classic (and often correct) "You aren't the target audience". For instance, I could write code on the Excel team (I don't). I am not a heavy Excel user, so my feelings on how Excel should be set up or operate likely do not represent the actual users of Excel and thus my feedback should be weighted lower than real (paying) customer feedback. Talk is cheap, people exchanging money for a product should be listened to above whiny devs (the 'whiny dev' label is intended to apply only to me and my feedback. External customers giving feedback are not whiny devs, at least not in my eyes :)).
Visual Studio is somewhat of an exception to this general rule because us oddball developer types (who don't represent the mainstream customer of most any product) actually do represent (mostly) the mainstream customer of our product.
>Another thing I can't wrap my mind around is how can it be possible to have one thousand of your customers yelling at you they don't like something -- that can be easily changed -- and have the management respond with "Oh well, we're still going to do what we want. What ya gonna do about it?!"
thousands << millions. The user base of Visual Studio is large, I don't know exact install numbers (I am sure I could find out, I just have never been curious enough to pester someone in marketing or the PM org) but I know it is definitely in the millions. It isn't clearly incorrect to argue that 1000 people playing with the beta may be a different group and have different beliefs than the millions of eventual users. I am not saying it is true or not, I haven't done the market research, but it isn't implausible.
Since the changes were quite drastic between beta and RC, my guess would be no, there was no study. If there was a study then I would question the competency of the people of carried out the study given how off the mark the results were (VS beta UI).
My guess is that the UX/UI people didn't really know what they were doing. They saw the massive backlash and went "Oh OK, I guess we were a little bit off. Let us remove most of these upper case captions, but we can't get rid of them entirely, so let's change the menu to upper case." When the second wave of backlash came (over the menu) the UX/UI people already had their pride bruised so they couldn't back down again.
Possibly, but I suspect it is, as they have already stated, driven by the desire to align some UX look and feel consistency across 'major products'. I don't know if I quite 'buy' the idea that all caps menus in VS and all caps menus in Office give you any 'alignment', but you know, I am but a dev not a UX person :)
Now, you send out the beta. You expect 1-3% or so of your customers to make a remark on it. Maybe 1‰ will contact you or write a blog post. Should that worry you? No.
And of course, you should be even less worried if you had measured performance related to the issue, and saw no differences.
In short: those thousands are self-selected and not representative of the audience. On top of that, all reviewers have to have some critique. Critisizing (nicely symmetrical, with all vowels being i's, and the symmetry of consonants; but I am digressing) such an obviously visible feature is easy.
On the other hand, when you include a designer in your product, you really have to let them do their job! Yes, feedback (external and internal) will be killer, but if they are good and know what they are doing, they won't let this sway them: they want to deliver a product that you will love, that you didn't know you wanted, and not necessarily what you asked for. Professional UX design with IDEs seems rather new (e.g., Cloud9), and developers are surprisingly a rather conservative lot. But if you want innovation from your IDE vendor, you should give them some room to experiment and possibly make mistakes.
(disclaimer: MS employee, but not working on VS)
(I don't know anyone inside Microsoft who likes the all caps, but at least Office apps have only 5 to 7 top-level menus.)
Or at least it appears that way from the screenshots in your link.
From my reading of corporate speak this appears to say that you can use Express Desktop 2012 (VNext Ultimate Web Cloud Edition :)) to write apps that target Vista, Windows 7 or Windows 8. Since WinRT is Win8+ only that would seem to imply 'down level' apps would need to be written in something else. The primary candidates would seem to be WPF/Silverlight, MFC, Winforms or Win32. Since Winforms/MFC are just thin wrappers over the Win32 APIs I think it would be torturous to try and make an IDE that allowed writing WinForms/MFC but somehow prevented direct Win32 access (especially given the ability to simply use pInvoke from managed code).