Visual Studio 2015 CTP 5 Available

http://blogs.msdn.com/b/visualstudio/archive/2015/01/16/visual-studio-2015-cpt-5-now-available.aspx

by trickz • 12 years ago

134 32 12 years ago

blogs.msdn.com

jarjoura• 12 years ago

I remember reading that Microsoft was moving the WPF framework into maintenance mode as they focus on the WinRT variant of UI development. Interesting that from the release notes, WPF appears to be getting feature development again. Hard to know without Windows 10 consumer announcements if Microsoft internally is back-tracking on the idea of fullscreen desktop apps.

mcintyre1994• 12 years ago

Windows 10 looks like it will feature windowed 'modern' apps so it'd be surprising if they didn't push those apps even further now.

_random_• 12 years ago

Enterprise backlashed and they had to respond. There is no need to suffer through backwards-compatible legacy stuff (JS, HTML, CSS) if you are not building something public-facing.

Encosia2• 12 years ago

Visual Studio itself is a WPF app, for what it's worth. I can't imagine Visual Studio being rewritten as a "Modern" app any time soon. So, it makes sense that MS will continue to invest in WPF.

aaronbrethorst• 12 years ago

Parts of VS may have a WPF UI, but I can assure you the vast majority of the codebase is C++.

tonyedgecombe• 12 years ago

I'm not expecting much, the roadmap is pretty underwhelming: http://blogs.msdn.com/b/wpf/archive/2014/11/12/the-roadmap-f...

putzdown• 12 years ago

Does anyone know how the support for C++11 is looking in this version? It would be pretty great if Microsoft could finally close [the gap](http://blogs.msdn.com/b/vcblog/archive/2014/06/11/c-11-14-fe...) on C++11 support a mere four years after GCC and Clang completed their support for the standard. That would also give some hope that Visual Studio might have full support for C++14 in a year or two (which GCC and Clang have today). Is there an updated support chart somewhere?

jbandela1• 12 years ago

They are making progress. The latest chart I saw (for the 2015 Preview ) is at

http://blogs.msdn.com/b/vcblog/archive/2014/11/17/c-11-14-17...

Someone• 12 years ago

http://blogs.msdn.com/b/vcblog/archive/2014/11/17/c-11-14-17... (via http://blogs.msdn.com/b/vcblog/archive/2014/11/12/visual-stu...)

eco• 12 years ago

Good to see the two things I've tried to use and wouldn't work in VC++ 2013 (generic lambdas and noexcept) have been implemented.

pjmlp3• 12 years ago

Microsoft is doing a mix of C++11 and C++14 support.

http://channel9.msdn.com/Events/Visual-Studio/Connect-event-...

Still, outside the open source world, from all vendors selling compilers, Microsoft is the most up to date.

Before anyone mentions ICC, no not even version 15 is fully compliant.

https://software.intel.com/en-us/articles/c0x-features-suppo...

IBM just realeased XLC with partial C++11 support.

Others are even worse.

TillE• 12 years ago

And odd bits of proposed C++17. Picking the low-hanging fruit, I imagine, based on their discussion of the difficulty in supporting other features.

I'm waiting impatiently for expression SFINAE. I like the features of C++ that let you write dynamic-esque code that's evaluated at compile time. It enables little bits of cleverness that save you from large complicated solutions.

outside the open source world

Which is quite large, considering that Clang and GCC are the standard compilers for just about every major non-Microsoft platform, including the mobile ones.

binarycrusader2• 12 years ago

I suppose I could see the "most up to date" argument, but Intel looks like it has the most complete commercial compiler at the moment for C++11.

But certainly, the next most complete support for C++11 in a commercial compiler might just be from Oracle Solaris Studio (which, despite the name, is available for Solaris and Linux both):

http://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#s...

It supports all C++11 features excluding: C++ 11 concurrency and atomic operations, and User-defined literals.

Notably, Oracle Solaris Studio is also one of the few compilers to include full C99 support.

ksk• 12 years ago

Historically Visual C++ has never been the goto compiler for anyone interested in the latest feature set. They have always had an amazing optimizer since they've had to build NT with it. I doubt they're ever going to catch up to GCC/Clang. msvc has to remain ABI compatible with other MS C++ libs like MFC/ATL/etc, and so ABI breaking changes have to wait for the next major version of VC. I think some stuff like COM has work across multiple VC versions without ever breaking.

buildops• 12 years ago

True. In addition, builds can sometimes be slow on MSBuild. Of course, if you're interested in cross platform development Visual Studio 2015 provides some great new features. Additionally, coupled with IncrediBuild (https://www.incredibuild.com/cross-platform.html) you can get some blazing fast builds

codingthebeach• 12 years ago

It would be nice if you wouldn't derail the conversation with another tired old "but it's not as good as gcc when it comes to X". This is a CTP. You split hairs over minor points of standards compliance that many devs won't even use on gcc yet because the features are so new, and completely avoid mentioning that the productivity of Visual Studio (for both .NET as well as native C++, including cross-platform C++) arguably dwarfs any other IDE on the market. Have you used, I mean really used, a recent version of Visual Studio for C++ work? Or are you making this comment because you haven't and you find it threatening? Tell you what. You build your C++ app with Xcode 6 or command-line gcc for all it matters. I'll build mine with Visual Studio 2013 or later. We'll see who wins. By the way, I love gcc. Love, love, love. That doesn't mean I have to take pot shots at Visual Studio, which is tooled to the Nth, completely stable, and not at all the old restrictive MS dev environment of yore. The times have changed.

flohofwoe3• 12 years ago

It is a fair question given the fact that Visual Studio 2013 doesn't even support basic C++11 features like constexpr. When doing multi-platform C++11 work the code usually must be dumbed down a lot if it needs to compile also in VStudio, e.g.:

- can't use many of the new initializer mechanisms in the class declaration (initializer lists, etc...)

- no constexpr

- std::chrono high resolution click isn't actually high resolution but only has millisecond accuracy

Complete list of missing C++11 features up to VS2013 is here: http://msdn.microsoft.com/en-us/library/hh567368.aspx

Microsoft should first complete their C++11 support before moving on to C++14, otherwise it will probably never get fixed.

Visual Studio is a fine IDE, but the C++ compiler lags behind quite a bit.

gurkendoktor• 12 years ago

Parity on standard compliance matters because many of us want to compile our code on different platforms, and that is all we download MSVC for. FWIW, it is also the only thing I look for in the gcc and Xcode/clang change logs.

taspeotis• 12 years ago

I was really surprised to read this:

    We have rebuilt the XAML language service on top of the .NET
    Compiler Platform ("Roslyn") to provide an improved XAML editing
    experience with rich IntelliSense that is faster and more reliable.

My understanding was that Roslyn was heavily geared towards languages that are largely procedural like C# and VB.NET. So functional languages, like F#, aren't suited to being parsed by Roslyn. But all of a sudden they're using Roslyn with a declarative language (XAML)?

seanmcdirmid• 12 years ago

XAML is a markup language, that counts as declarative, but you can think of it as a subtraction of C# (the ability to create instances and bind their properties), it doesn't add any advanced declarative programming features and definitely nothing fancy type-wise as in F#.

I don't know what they did, but it seems reasonable that it would share a type checker with C# but have a unique parser.

useerup• 12 years ago

Having used XAML recently for purposes not even related to WPF, I can definitively see what this might bring.

XAML is at its core a format to describe an object graph declaratively. The objects can be any .NET object.

The current XAML editor already understands a lot about the objects you describe - i.e. it loads the assembly and introspects the types to give you intellisense while editing. The current one is not without its quirks and bugs, however.

I'd be thrilled to have a new, robust editor that intrinsically understands classes, properties, value converters etc to offer more assistance when writing raw XAML.

graycat• 12 years ago

Apparently

VS -- Visual Studio

ALM -- Application Lifestyle Management

CTP -- Community Technology Preview

TFS -- Team Foundation Server

Visual Studio 2015 CTP 5 Available

Related Stories