The official source of product insight from the Visual Studio Engineering Team
Today, we're excited to announce that Visual Studio 11 Beta is now available for download.
Back in September, we announced the release of Visual Studio 11 Developer Preview and detailed the simplification efforts we made across the IDE, integration of the best and most popular features from the Productivity Power Tools and effort to improve project compatibility scenarios.
Since then, we've been busy improving and fine tuning experiences in Visual Studio and also addressing feedback and known issues from the Developer Preview. We’ve invested in performance improvements in the areas of responsiveness and memory utilization.
Take a look at what's new in Visual Studio 11 Beta and .NET Framework 4.5 Beta on MSDN and for a more in-depth discussion, see Jason Zander’s discussion of the Beta release . 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 revealed the new developer experience (in Part 1, Part 2) and showed you screenshots of the new user interface, iconography, search capabilities and how we've streamlined common workflows. Many of you had a lot of passionate feedback on these posts. We have read all the comments, and you will hear more about this from us soon. In coming weeks, we’ll be using this blog to talk about many of the other specific features of Visual Studio 11.
Your feedback is an important part of our software development cycle. We review every comment that we receive and are constantly using this feedback to improve the product. Now that the Beta is available, we hope you will install and work with it, and continue to send us your feedback on how it all comes together.
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
Are there any improvements for VS extensibility? I think that this is still one of the weak points of VS (compared to the relative ease of development of extensions for Eclipse for example). The new managed APIs for VS2010 were a step into the right direction. Have there been further improvements?
I left a comment earlier hating the new colors, but after looking at the light theme it looks relaxing, but that is after a few minutes of use.
I hope there is an option of a colorful theme, but the light one also looks ok.
Like many have said, there's no way I could look at this day in and day out. The "chrome" of VS 10 was actually done well. VS 10 is a dog performance-wise compared to VS 2008, but I'm not sure if the "chrome" attributed to that. If the chrome isn't the major slow-down, I'd really like to see you put the same VS 10 chrome/lines back. With the color-theme editor extension for VS 10, I could tweak the colors to my liking. Also regarding icons, I agree with others that when I glance up at the toolbars, the specific colors of the icons helps me be more productive by locating them quickly.
Please bring back the chrome/lines of VS 10, and for those using the theme extension, how about actually using that extension (instead of re-inventing the wheel) and give us a few new "themes". It just seems so logical to use the extension already there as a vehicle to provide alternate themes to your users.
Very ugly - looks like old DRDos style app.
When you uninstall Visual Studio 11 Beta, and Visual Studio 2010 stops working then you need to either repair Visual Studio 2010 or reinstall Visual Studio 11 Beta or newer release. This should fix the majority of issues that arise.
Visual Studio PM (setup owner)
I get what you're saying about putting the UI in the background to focus on the code, but it seems to me that you are solving a problem that doesn't exist. Has anyone seriously had a problem being "distracted" by toolbars with colors in them? I can only assume that we are being trolled by the Visual Studio team.
If Visual Studio had always looked like rubbish, it would have been acceptable, but the fact that they actually spent resources to make it this way blows my mind. I can only assume we are being trolled; if so, well played.
New visuals (colors, big fonts, icons) ars simply bad.
No really big improvements in functionality and features.
Languages VB/C# have only new asynchronous support, and nothing more - too little
If you need async, you can use Async CTP. No new VS 11 is required.
NET 4.5 with lot but small changes, over 4 - too little
Overall - no true reasons to jump on new VS, especially with his new terrible look.
New VS 11 requierd only for develop Metro apps.
The responsiveness is far better than in VS10. This is very good news! I really like that I can use the whole UI when the project compiles. Finally. Thanks.
... when the project is compiling.
Where are the Windows 8 project templates in the professional setup? It seems there is only a Express edition for Windows 8, but that can be installed only on Win 8.
Will it be possible in the final VS version to develop Windows 8 WinRT apps on a Windows 7 computer with the emulator? I don't plan to update my desktop development system to Windows 8, just my convertable laptop.
After using VS11 Beta all day long, I have to admit that is not so bad as screenshot looks and i love the C# colors of the new Dark theme, but i found really slower find what i'm searching because of the lack of colors.
The :::: ALL CAPS :::: title are really ugly, so please remove it!
It disappointing that i cannot decide what install, VS is a software for skilled users, not for secretaries so i must have installation customization options as VS2010 provides.
Agreed with Massimiliano, we need to decided what to install.
And it's just takes toooooooooooooo long to install.
I don't need F# and Expression, so don't install them!
Finally, finished, took about an hour to install.
It is faster than VS2010, a LITTLE faster, but I'm sure the RTM version will be a LOT faster, right? Please don't diappoint me.
I like the new WPF editor, by the way.
The UI is a mess, this gonna take more than an hour to get used to.
The dark theme didn't get applied to everything. I can live with the old-fasion Options dialog, but what about the Add New Project dialog? And the Project Property page, it's still in gray!
Maybe it's just me but the default Consolas font looks weird under dark theme, Courier New is much better, but I don't like it.
When I focused on the code... Nope, can't do, the ALL GRAY thing just too distracting.
And why is Visual Studio shouting at me? It says:
GET OUT OF MY SIGHT!!!!!!
At the end of the day, I think I'll keep VS11 beta on my computer, for a while.
I'll provide more feedback after I done some serious work with it. I'm currently working on a script based game engine under VS2010, luckly the project format didn't changed.
Ok, time to get working and get serious...
SHUT UP! SHUT UP!!! SHUT UP!!!!!! I'm gonna hide you, ALL OF YOU!!!!!
Sorry about this many posts, but I'm sure you want the feedbacks as soon as possible.
I have encountered a problem which force me return to VS2010. When I tried to debug my project (which was created in 2010, C++ project), VS11 pops up a message box shows:
Unable to cast object of type 'Microsoft.VisualStudio.Project.ConfiguredProjectCache~1[Microsoft.VisualStudio.Project.Immutables.ImmutableHashMap~2[System.String,System.Threading.Tasks.Task~1[Microsoft.VisualStudio.Project.PropertyPages.PropertyPagesCatalog]]]' to type 'Microsoft.VisualStudio.Project.ConfiguredProjectCache~1[Microsoft.VisualStudio.Project.Immutables.ImmutableHashMap~2[System.String,Microsoft.VisualStudio.Project.PropertyPages.PropertyPagesCatalog]]'.
Then failed to start.
This is probably because I use VS2010's Platform Toolset (which is v100). But the compile process completed without error, I just don't understand why debugging failed. (Of course I have VS2010 installed side-by-side, along with XNA4, WPSDK7.1, Silverlight 5 Tools).
Another try (to start the debugger) got a different message box shows:
The "WindowsLocalDebugger" rule is missing the "LocalGPUDebuggerTargetType" property.
The problem gone after I changed the Debugger Type to anything (for example, "Mixed"), start the debugger, it failed again , the first message box is identical, the second one changed to:
The "ConfigurationGeneral" rule is missing the "VSInstallDir" property.
Then change it back to Auto. Everything is fine now, strange.
BUT! After I restarted VS11, the problem returns, I have to do the above all over again. It's annoying!
This problem can be reproduced with a new VS11 win32 console project, so I'm sure it's not my problem ^_^
And if the Platform Toolset is v110, everything is fine.
PS.Tried to fill the bug through connect, but my registeration keep failing (I get "Bad Request - Invalid Header" all the time). I have filled a suggestion through connect in the past, I don't know why I need to register again...
PS2.Hopefully my pool English didn't give you too much trouble ^_^