The official source of product insight from the Visual Studio Engineering Team
Today, we're excited to announce that Visual Studio 2012 RC is now available for download on our Visual Studio product website.
Since the release of Beta, we’ve been hard at work making final touches, addressing top customer feedback from Beta, and improving performance across the IDE. Take an in-depth look at what's new in the Release Candidate (RC) of Visual Studio 2012 RC and .NET Framework 4.5 on Jason Zander’s blog. We also encourage you to check out the new Windows 8 App Developer Blog to learn more about how to build great Metro style apps for Windows 8.
Last week, we gave you a sneak peak at the user interface updates coming in RC and even gave you a behind the scenes look at what’s coming in RTM for the dark theme. Keep an eye out for upcoming posts here on the Visual Studio blog as we have a great line up planned.
If you encounter a bug or an issue, please report it through the Visual Studio, LightSwitch, and Blend Connect sites. We also want to hear your suggestions or feature ideas/improvements so please add your suggestions to UserVoice or vote on other user’s suggestions.
The Visual Studio Team
I vote for a logo change. It's so ugly. This sort of flat square design is awful. I understand this is for tablets, but do we have to suffer for downgraded features when using PCs, only because a couple of developers will use tablets to use VS?
Thanks for some color in icons. But we need more.
More color needed in icons in "New Project", "New Project Item", "Extension Manager", all toolbars, intellisense and, maybe, solution explorer. If you hate color so much, make it a option. Or maybe reveal the colors when mouse moves away from the code?
Gray on grey icons are useless - every designer will tell you how important the colors are. You made the Blend better, but crippled the Visual Studio in the process.
Visual Studio deserts Metro. I even created a comparison image for you:
Please bring back the colored icons from 2010. It's so hard to be productive with these dark gray icons (RC). Also, why 500,000 users (or however many use VStudio) choose from just 2 themes, especially when those 2 are so controversial??? MS always talks about "partners"...can "partners" developer more themes???
Btw if anybody is interested I wrote and extension that removes the ALL CAPS and also the custom window chrome, since that was also a terrible idea. It will probably break with the final release since it worms its way pretty deep in there...but hey, it works now.
Some dude > Awesome extension, thanks a lot!
Unfortunately the custom chrome doesn't get removed when launching VS by opening a file or a solution from Win Explorer. Could you have a look? Thanks!
Great work in the latest release. I <a href="www.etabakov.com/.../my-impressions-after-developing-with.html">posted my impressions</a> after using VS 2012 beta and the RC for a few weeks as a primary IDE. I hope you find my feedback useful.
it seems that WinForms for C++/CLI is gone :-(
so what was the point in reintroducing Intellisense for C++/CLI?
What a joke. I took the time out to install Windows 8 and Visual Studio 2012 "Release Candidate" and I can't even create a Metro project because of errors. KNOWN errors. Pathetic! This is a release candidate? We're all doomed. This KNOWN error shouldn't have made it into the Alpha release.
What a joke.
@Larry Anderson - could you grab a callstack using the instructions here: blogs.msdn.com/.../how-to-obtain-debug-information-from-a-hung-frozen-application.aspx ?
Then use the VS Feedback tool to attach the .dmp file and report the bug to Microsoft.
REG_DWORD value: 1
@Some dude: Much better, thanks!
C# intellisense doesn't see variables declared in XAML.
It's a joke. But it's not funny.
Instead of _improving_ functionality of VS you have spent years killing UI. Well done boys, update your CVs - You will need it soon
Dear Visual Studio Team,
In concluding your last blog post you wrote: "We also want to hear your suggestions or feature ideas/improvements so please add your suggestions to UserVoice or vote on other user’s suggestions." Why do you want to hear our suggestions or ideas for improvements? Why? You've just spent the last three months ignoring the majority of suggestions and ideas for improvements when it comes to the UI.
I'm amazed at your willful disregard for your user base. If there was one request that appeared repeatedly over the last three months, it was to please add color back to the Solution Explorer icons. Time after time, developers commented that they found color in Solution Explorer to be immensely helpful. It was stated repeatedly: when you make all the icons in Solution Explorer the same color you make their work harder.
I'm at a loss to understand your stubborn refusal to adding meaningful color to Solution Explorer despite constant requests for it from users. I really just wish you would be honest with the community and stop with the patronizing "we want to hear your ideas" nonsense.
Here, I'll give you some helpful text you can copy and paste into your next blog post: "Hello everyone, feel free to give us your thoughts about the new UI design but be assured that ultimately we're going to do whatever the hell we want because, well, we can. Thanks and have a wonderful day."
"In concluding your last blog post you wrote: "We also want to hear your suggestions or feature ideas/improvements so please add your suggestions to UserVoice or vote on other user’s suggestions." Why do you want to hear our suggestions or ideas for improvements? Why? You've just spent the last three months ignoring the majority of suggestions and ideas for improvements when it comes to the UI."
Why, because if the majority will say that they like the flat, low-colors, all-caps UI, it's "you've asked for it and we delivered!" And if the majority will say that they don't like it, it's "only a small number of our customers visit these forums, our user base is much more diverse than that".
On a serious note, I think they are asking users for their opinion, because it is weird not to do that, nothing else. They don't listen to their users and then decide what to do, they first decide what to do and then attempt to justify it from what they hear from users. This doesn't always work, but that's fine.