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
I would like you to please consider and read the following article...
and then have a look at this:
Please at least take this into consideration... I specially like the comment made by RubenP on the first article at Tuesday, June 05, 2012 9:18 PM as a answer to Allen Chen [MSFT] s comment...
In this new version of Visual Studio 11 will it resolve the issues of excluding files from a project. As soon as I do this , the excluded files will get flagged as candidates for deletion in the pending changes window. This seems to be a known issue from Microsoft, and from what I've gather reading, the only know workaround is to manually edi the project file to remove this entry. Is this issue resolved??
wtf are you people doing?
I'd like to see the internal communication(s) between this developer and chip-makers like intel, etc, etc.......
I do not like the new Visual Studio at all. I do like the look of the Metro OS, but I can't stand the new visual studio. Is is possible to install my VS2010 Ultimate on Win8, and build metro apps that way?
Unbelievable that .Net 4.5 is not running on XP. 30% our customer use XP. We as partner http://www.woax-it.com/ have now big problems. We can not switch to 4.5, but we need the features and the lot bug fixes in WPF .Net 4.0
buhahahahahahahha.....what the bull *** ez this?/.
I don't want to write 'Metro' applications, I want to write applications full stop!! I'm gob-smacked at how for years we've been seperating the various layers i.e. application layer and a style layer, but now I'm being told that it's all wrapped up in one again!!! Or am I getting this wrong?
I don't really understand why anybody would want to write an app, that will only work on one OS and the look is determined by the OS not the designer. But then I've only been coding for 30yrs, what would I know!!!
Microsoft are completely within their rights to do this, however that doesn't mean they're not insane to do so! If they imagine that corporate developers (i.e. those who can afford to pay $500+) will create some of the innovative software that made previous versions of Windows useful to a majority of people, then they really haven't got a clue what they're doing.
This is another slide into the death of Windows as far as I'm concerned. One wonders how they spent so much time making an OS with so little use. My use of it stops right here. I will NOT be buying or installing the 'fixed' Windows 8 (i.e. Windows 9). As soon as I find my product key for the Windows 7 I replaced with this horrible Windows Hate, I'll be reinstalling it and then get back to writing proper applications again. Windows Hate and all the accompanying accessories can f@ck off as far as I'm concerned.