The XAML design tool that shipped as part of Expression Studio, and where its documentation survives after the suite was discontinued.
Microsoft Expression Blend was a visual design tool for XAML interfaces, sold inside Microsoft Expression Studio and discontinued as a standalone product in December 2012. Its documentation is scattered across three eras: the standalone product, the archived vendor site, and the successor inside Visual Studio.
This entry collects the sources that still resolve, grouped the way this catalog has always grouped them, with a note on what each holds and where version boundaries are likely to mislead.
Expression Blend was Microsoft's design tool for XAML interfaces. It was announced as Expression Interactive Designer, renamed to Expression Blend in December 2006, reached its first public preview on 24 January 2007 and shipped that April. Its purpose was to let a designer work on a Windows Presentation Foundation or Silverlight interface visually, producing the same XAML a developer would otherwise hand-write, so that the two roles could work on one artefact instead of exchanging mockups.
The product sat inside Microsoft Expression Studio alongside Expression Web, Expression Design and Expression Encoder. Version 3, released in 2009, is the release most contemporary reviews discuss, and it is the version that introduced SketchFlow, a rapid-prototyping mode that produced clickable, annotatable prototypes rather than finished markup. Expression Studio reached its final release, version 4.0, on 7 June 2010.
In December 2012 Microsoft discontinued the standalone Expression suite. Expression Web and Expression Design were retired outright; Blend was moved inside Visual Studio and continued as Blend for Visual Studio. That is the pivot that makes the tool confusing to research: the same name describes a standalone product with its own release history and, afterwards, a component of a much larger one.
Sources that name the product directly. The lifecycle record is the one to read first, because it settles support dates that secondary writing gets wrong constantly.
Microsoft's own lifecycle record for the Expression products: release dates and support end dates, per version. The authoritative answer to when a given release stopped being supported, and the only one that does not need cross-checking.
Last checked 2026-08-26 · reachable
The encyclopaedia article covering both eras: the standalone Expression Blend releases and the later Blend for Visual Studio. Follows the renaming from Expression Interactive Designer onward, with citations for each step.
Last checked 2026-08-26 · reachable
The suite article. Useful because Blend was never sold in isolation for most of its life, so the licensing questions and the 2012 discontinuation only make sense at suite level.
Last checked 2026-08-26 · reachable
Where the successor product and the original marketing material live. The archive entry matters more than it usually would, because the product site itself was retired rather than redirected.
The successor. Documentation here describes the XAML designer as it exists inside Visual Studio, which is close to the original in purpose and quite different in workflow. Read this for what the tool is now, not for what Expression Blend 3 was.
Last checked 2026-08-26 · reachable
The Expression product site as it stood before retirement, including the feature descriptions and the SketchFlow material for version 3. Because the live site was withdrawn rather than redirected, this is the only route to the original vendor copy.
Last checked 2026-08-26 · reachable
Discontinued developer tools have a specific research problem: the vendor documentation is usually preserved somewhere, but the version boundaries get flattened. A page written about Blend in 2009 describes a standalone product with SketchFlow and its own installer. A page written in 2015 describes a panel inside Visual Studio. Both are correct and they are not about the same thing.
The reliable order is to fix the version and the date first from the lifecycle record, then read anything else with that version in mind. Where a source does not state which release it is describing, treat the date of the source as the version indicator, with December 2012 as the dividing line.
This is also a good illustration of why vendor documentation is a stronger citation than commentary. The lifecycle page is published because Microsoft has support obligations attached to it, which is a durable reason for a page to exist. Commentary exists while somebody chooses to host it. The website data section makes the same argument about registry records against vendor metrics.
Not as a standalone product. Microsoft discontinued the standalone Expression suite in December 2012 and moved Blend into Visual Studio, where it continues as Blend for Visual Studio. Expression Web and Expression Design were retired without a successor.
Designing XAML interfaces visually for Windows Presentation Foundation and Silverlight applications. The output was the same XAML a developer would write by hand, which was the point: designer and developer worked on one file rather than exchanging static mockups.
A rapid-prototyping mode introduced in Expression Blend 3. It produced deliberately rough, clickable prototypes that reviewers could annotate directly, separating the question of whether a flow worked from the question of how it should look. It is the feature most reviews of version 3 lead with.
Two places. Microsoft Learn keeps the product lifecycle record, which is authoritative for versions and support dates. The original marketing and feature pages were withdrawn rather than redirected, so those survive only in web archive captures of the Expression product site.
Every entry is a curated list of sources for one term, annotated and dated. The catalog index lists all of them.
How an appendix is built and placed in academic writing, with the style authorities that define it.
Open the entryWhere papers are indexed, hosted and made openly readable, and which archives are stable.
Open the entryThe browser era of a mobile phenomenon, and what remains playable after Flash.
Open the entry