Current and future Microsoft (Expression) Blend Versions

Any Developer working in the XAML Environment must have stumbled across Microsoft Blend, a.k.a. Expression Blend at some time. Blend is a Software aimed to support developers and designers of XAML based UIs create designs and animations, apply behaviors and so forth.



As of 2010 (talking VS Versions), Microsoft has made the licensing of Blend a real mess, if you're a WPF Developer: The only way to purchase Blend is buying the entire Expression Studio Ultimate for somewhere around 500 Euros. Smaller development teams are made to bleed unnecessarily, since the VS 2010 XAML editor had serious issues before SP1.



We're talking 2012 now - seems MS have learned their lesson: Blend is free for Windows 8 Store Apps and comes along with the correlating Visual Studio Express Edition. But what about WPF or the already zombified Silverlight? Good news first: Blend will continue to support WPF. But what are the licensing terms? Looking things up on the Blend Insider Blog, I found the following table:

Platform Go live Blend version
Windows Store apps, HTML Blend for Visual Studio 2012
Windows Store apps, XAML Blend for Visual Studio 2012
Silverlight 4.0 Expression Blend 4
Silverlight 5.0 Expression Blend Preview for Silverlight 5
WPF 3.5/4.0 Expression Blend 4
WPF 4.5 Microsoft Visual Studio 2012 Professional
WPF/Silverlight Prototypes Expression Blend 4

That seems to be the choose-your-destination-and-go-for-it map, but honestly - am I the only one a little confused now?

Well, for me Lori Dirks has made it clear:
Blend is not included in Visual Studio 2012 Express for Windows Desktop. If you want to develop for the desktop (SL/WPF) you'll need to use the Blend version that is appropriate for the platform you're targeting.
So, I'll stay with Blend 4 for Applications targeting .Net 3.5 and 4.0 and switch to VS 2012 Professional for .Net 4.5. Why so complicated? Why not just one version of Blend serving all purposes? Well, we shall see how Visual Studio 2012 can replace Blend...I'm rather sceptic concerning the animation features, UI State Recording and their like.

Update: Obviously the common call for clarity has had some effect. Here's the new direction:


  • Blend will continue to ship as a standalone tool with Visual Studio 2012, as part of a consolidated designer/developer offering. Blend for Visual Studio 2012 provides a rich design-centric environment for building Windows Store apps and Windows Phone apps. In addition to that, WPF, Silverlight and SketchFlow support is available today as a preview and will be released in Visual Studio 2012 Update 2.
  • Expression Studio 4 Ultimate and Expression Studio 4 Web Professional are no longer available for sale. For customers who previously purchased these products, all components within Ultimate and Web Professional will be supported through their support lifecycle.
  • Expression Design 4 and Expression Web 4 are now available for download at no charge. Technical support will not be available for these free versions.
  • Expression Encoder 4 Pro will be available for purchase through 2013. Expression Encoder 4 remains available for download at no charge.

    • Kommentare

    Kommentar veröffentlichen

    Beliebte Posts aus diesem Blog

    WPF Diaries : Using HLSL pixel shaders

    HLSL is mature language that enables developers to address the graphics hardware in a familiar, C-like way. Next to vertex shaders, you can use it to write pixel shaders, which is what - with .Net version 3.5 SP1 - Microsoft introduced into WPF. What sounds like no big deal at first sight is a major leap towards serius WPF / Silverlight game development and - more generally - graphically intensive UI. That goes hand in hand with the DirectX-powered concepts of WPF, finally giving .net developers a good deal of acceleration without the need for unsafe code. Since we're not doing heavy calculus on our GPU, even decent hardware is sufficient to display manipulated images. Since the death sentence of XNA , hopes were shallow that .Net developers get in touch with this cool technology, but we've always loved the walking dead, haven't we? Quite a few WPF Pixel Shader libraries and tutorials have popped up (Some are linked below), and I really recommend getting in touch with the
    Mehr anzeigen

    Getting the Crisp back into your WPF Apps

    Bild
    WPF has a lot of advantages, it's perfectly sane data binding mechanism being one of the most outstanding ones.On the flipside, many people (meaning companies, mostly) have refused to switch from WinForms to WPF because of the "blurry" looks of applications written in WPF. This blurryness goes back to two mechanisms: 1)Text Smoothing Instead of relying on the system's ClearType mechanism, WPF does it's own thing-a-magic, which is blatantly inferior to the aforesaid. In fact, WPF smoothed fonts are a definite way to headaches, if read for some time. Note : The image is from a website that compares various Microsoft.Net Font-Smoothing implementations. They might be useful to integrate text in images, though.For business applications (displaying data grids etc.) this is a K.O. criterion. Nobody wants to have to take their glasses off in order to achieve readability, and nobody wants their software deployed along with a pack of aspirins. 2)SubPix
    Mehr anzeigen

    WPF and Workflow Foundation : XAML parser compatibility issues

    I am absolute and unrestricted proponent of the Windows Presentation Foundation , and I think I cannot say this often enough : It makes things easier and more structured. And I love it, somewhere close to every day. Now, as three quarters of this year have passed by without any significant smoke rising, I have also had the chance to get to grips with Workflow Foundation , and was literally astounded to see how far Microsoft has taken the idea of XAML (Yes, I'm a bit late to that party).  Combining the two technologies was the next obvious step, which worked fine until yesterday.  Here's the story:  In my somewhat completed WPF UI, I added a WF Activity. An instance of that Activity could not be created, Visual Studio kept throwing "Namespace or Type not found" like it was candy. Funny, though, that intellisense proposed both the class and the containing namespace of the Activity. A more complete description of the issue can be found in my StackOver
    Mehr anzeigen