The official source of product insight from the Visual Studio Engineering Team
Today, we want to share the final product lineup and specifications you can expect to see for the next release of Visual Studio. This also includes system requirements and platform you can develop for with Visual Studio 11.
If you would like to use a language specific Express edition (C# Express, Visual Basic Express, or C++ Express) without specialized tooling for the latest platforms, you can use the Visual Studio 2010 Express editions, which will continue to be available as free downloads.
A common question that we’ve received since the Visual Studio 11 Beta release is related to tooling support for Windows Phone and Windows Azure. To make sure customers have the latest tools with the latest platform offering we’ll be releasing Visual Studio Express for Windows Phone with the next release of Windows Phone. Similarly, Windows Azure tooling will be available in conjunction with the next Windows Azure update. Until then, you can continue to use Visual Studio 2010 Express for Windows Phone to create Windows Phone apps, and Windows Azure SDK for .NET (with Visual Studio 2010) to create Windows Azure cloud services.
Finally, LightSwitch, which launched last year as an out-of-band release, is now officially part of the Visual Studio 11 core product family. LightSwitch features will be available through Visual Studio 11 Professional, Premium, and Ultimate editions. For more information, please visit the LightSwitch team blog.
As you have seen in our earlier series on Visual Studio 11 performance, we’ve made some significant investments in performance this release. We are excited about the feedback we’ve received so far and have been working to make the experience even better for RC. We are happy to announce that Visual Studio 11 hardware requirements will be the same as Visual Studio 2010’s. If you are working now with Visual Studio 2010 you can enjoy the new performance improvements in Visual Studio 11 without any additional hardware investment.
Visual Studio 11 leverages core capabilities that are only present in the latest versions of Windows. For this reason Visual Studio 11 requires Windows 7 or higher to run.
To help you take advantage of the latest features, the default target for applications created with Visual Studio 11 will be set to .NET Framework 4.5 (for managed apps) and the VC11 toolset (for native apps). Both will allow your apps to run on Windows Vista and higher. However, if your app needs to run on Windows XP or Windows Server 2003, you can still use multi-targeting to make sure your application will run on those platforms too.
C++ developers can also use the multi-targeting capability included in Visual Studio 11 to continue using the compilers and libraries included in Visual Studio 2010 to target Windows XP and Windows Server 2003. Multi-targeting for C++ applications currently requires a side-by-side installation of Visual Studio 2010. Separately, we are evaluating options for C++ that would enable developers to directly target XP without requiring a side-by-side installation of Visual Studio 2010 and intend to deliver this update post-RTM. You can find more information on C++ multi-targeting here.
For details on today’s announcement visit the Visual Studio 11 website.
The Visual Studio Team
@Chris and others (@Paul, @grumpy, ...):
(I have posted this already on vcblog, but I think it is important enough to post it here as well, read on and hopefully you will agree with me.)
"This is frustrating. Post-RTM, how much later? And notice how they say they are still evaluating these options, it's not a sure thing. This evaluation has lasted for 4 weeks now. The low complexity (it's simple) of making XP targeting available does not justify delaying it for post-RTM."
The biggest issue is not this, the biggest issue is that they still seem to be talking about supporting XP via multi-targeting to a different compiler. The "option" they seem to be evaluating is likely a checkbox in the installation package for VS11 which reads "support for XP" and installs the compiler from VS10. They are solving the wrong problem. They are helping a couple of people for whom multi-targeting is a solution. They are NOT helping the majority of the people for whom multi-targeting is NOT a solution, not at RTM, nor post-RTM.
@Chris, how about C++ Builder ? C++ 11 for Windows/Mac/Android/iOS ? With a great IDE ? and great frameworks like VCL/FireMonkey ?
> Separately, we are evaluating options for C++ that would enable developers to directly target XP without requiring a side-by-side installation of Visual Studio 2010 and intend to deliver this update post-RTM.
Does this mean that post-RTM will allow the VC11 compiler to directly target XP, thus allowing us to use C++11 on XP? Please, a clear answer instead of stalling us C++ developers yet again.
Nearly a 1000 comments in the previous post, mostly discussing a particular issue, and you don't address that issue in the next blog post?
On that issue I would suggest that Metro design guidelines are not applicable to Windows development, which includes the VS IDE. I guess we're going to have dozens of frankenstein user interfaces. You'd think VS would be immune to that.
Visual Studio 11 Express will not be able to target pre-Win8? Do you realize how many open source developers this will hinder? You seem to have totally lost the connection to your users. Good riddance.
"Visual Studio 11 Express for Windows 8 provides tools for Metro style app development. To create desktop apps, you need to use Visual Studio 11 Professional, or higher. In addition, Visual Studio 2010 Express products - Visual Basic 2010 Express, Visual C++ 2010 Express, and Visual C# 2010 Express - will remain available for free download."
Is the person responsible for these decisions trying to sabotage Microsoft?
The ability for Express editions to create desktop apps isn't something you had to create because it was already there. So...you're just taking out existing functionality to try and force development of Metro apps???? How raw can you guys get??? I really thought the "evil" of Microsoft was actually gone. Still runs in the veins I guess.
RE: Express editions can no longer create desktop apps...
evidence that MS is scared that Metro might not succeed (on its own) without twisting people's arms. Talk about lack of self-confidence...
I would not be surprised when they'll later postpone Windows XP support to next version - just as any other bugs which never got fixed in the current release and always promised to be fixed in next version.
When it is time for the next version (VC++ 12) support for targeting Windows XP had been dropped as Windows XP is no longer supported.
Therefore I would not expect to have Windows XP as target for VC++ 11 and we'll be forced to used multi targeting feature but can't benefit from the C++ languages enhancement in VC++ 11.
Is there a WPF designer of good quality in VS 2011? Hand editing xaml in vs 2010 is slow.
What? No VS Express for non-Metro apps?
Considering the quality of other IDEs, I'd bet VS will soon be cracked as much as Photoshop...
interesting, see www.microsoft.com/.../compatibility
native remote debugging not available for Vista. So even though its a native targeted platform there's no way you can debug on it. Windows 7 and above is the only platform you can debug on.
another interesting thing left out "Windows Server 2008" non-R2 (i.e. Windows Vista Server) is completely left out of the chart.
Please, add threads windows to the Express. With today multi-core era, this is very basic tool for development
1 in every 3 or 4 instances of our application runs on Windows XP (25% - 33%). We can't leave XP behind right now, but I appreciate that this move (while it hurts) might help us in the medium- to long-term.
Guess I am waiting for VS 12 and .net 5.0. There is no point in upgrading to vs 11 just so I can do what VS 2010 does now (target .net 4.0 for xp support).
I imagine VS 12 will be out when XP goes off support (2014). I will just have to wait till then (I hope vs 12 support windows 7).