It is finally Spring in Seattle, and it’s Mix in Las Vegas. Many of you, our faithful Expression Blend customers, have become accustomed to also see a new version of Expression Blend blossom with the flora of the land.
Wednesday, April 13, 2011
Thursday, September 16, 2010
A customer just asked the question how to scroll a ScrollViewer at design time in Blend to manually design content for it that goes beyond the visible viewport size.
Wednesday, September 15, 2010
The mission of the Expression team at Microsoft is to deliver great tools that enable designers and developers to create outstanding user experiences.
As I wrote in a previous post, the Expression at Microsoft team is hiring for a number of positions across the team, including product design, PM, UX, dev and test.
Here are links to the different job descriptions of some of the open PM and UX jobs. If you are interested in building great design and development tools and you have the right skills, we’d love to hear from you.
- Senior Program Manager, HTML Designer Tools
- Senior Program Manager, XAML Designer Tools
- Senior Program Manager, XAML Designer Tools
- Senior Program Manager, SketchFlow Prototyping Tools, in Minnesota
- Senior Program Manager, Visual Tools for Developers
- Senior UX Manager
Tuesday, June 8, 2010
Several customers asked on Twitter today how to navigate to another screen when a storyboard is finished playing.
The answer is: There is a StoryboardCompleted trigger that you can use together with any action, including the Navigate actions. This post describes how to use it.
Sunday, June 6, 2010
If you have been using the path list box introduced with the preview versions of Expression Blend 4, here is something fun for you…
Sunday, June 6, 2010
We have demonstrated Expression 4 at Mix 2010. And today, Expression Studio 4, including Expression Blend, Web, Encoder and Design has officially been launched at Internet Week in New York, and will be available shortly.
There is a new SKU line-up and, very importantly, free upgrades for Expression 3 users. Please see www.microsoft.com/expression for more information.
For more on Expression Blend 4 specifically, you might also want to have a look at my previous post from Mix 2010:
Introducing Blend 4 – For Silverlight, WPF and Windows Phone
Also, on this blog you can find a series of articles about one of the fun creative features in Expression Blend 4, path-based layout, which begins here:
Blend 4: About Path Layout, Part I
Before this post comes to a close, I’d like to use the opportunity to thank our very active customers for a lot of great and encouraging feedback – without your interest and excitement, Expression would not be the same. And thanks to the amazing team that I have the honor to build Expression with
So much for now. Please stay tuned and most of all, have fun with Expression 4!
Sunday, April 4, 2010
Sorry for the long delay. Here’s another installment of my series on path-based layout.
In our demo at Mix 2010, we showed that path layout can also provide a neat stand-in for some features that are missing from the Silverlight runtime: Motion path and text on a path.
Let me show you how these are done. Also, I’m going to give you a sneak preview on some other more advanced stuff you can do with path layout that my colleague Joanna Mason is going to blog about in detail soon…
Wednesday, March 24, 2010
In today’s installment of my series on path-based layout, let me show you that path-based layout can actually be used for dynamic, resizable layout
Wednesday, March 17, 2010
In the previous installment of this series on path layout, I explained how to add a rotation offset to an element in the list box while keeping well-fitting highlights. I also promised that I’d explain in greater depth what is going on.
As a side benefit, you will also learn how to change these pesky blue selection highlights of a list box.
The next post in this series will be back to focusing on path layout itself.
Wednesday, March 17, 2010
Ok, I’m back for part II of my short series of posts on path layout (see here for part I). Let’s continue where we ended last time:

