Expression Blend and Design

The team blog of the Expression Blend and Design products.

.NET Framework 3.5 Service Pack 1 Beta and Expression Blend

.NET Framework 3.5 Service Pack 1 Beta and Expression Blend

  • Comments 27

Recently, a beta of .NET Framework 3.5 Service Pack 1 was released. There is currently an incompatibility with Expression Blend/SP1, Expression Blend 2, and Expression Blend 2.5 March 2008 (whose version number is 2.1.1111.0) where Blend will not work if you have .NET Framework 3.5 SP1 Beta installed.

We currently have a version of Expression Blend 2.5 March 2008 Preview (referred to as Blend 2.5 Preview from now on) that fixes this incompatibility, but you will only be able to create and edit WPF and Silverlight 1 projects. While Blend 2.5 Preview will also allow you to create and edit Silverlight 2 projects, they are not supported by Visual Studio at this time.  If you are doing any Silverlight 2 development, please do not install .NET Framework 3.5 SP1 Beta until a future Silverlight Tools update is made available.

Download Updated Blend 2.5 Preview
If you downloaded and installed a version of Blend 2.5 Preview prior to May 9th, please uninstall your existing version of Blend 2.5 Preview and install the updated version of from the following link:

blendicon Download Refresh of Expression Blend 2.5 March 2008 Preview

Once you have the latest version of Blend 2.5 Preview installed, you can verify that you are running the latest version if your build number is 2.1.1113.0 by going to Help | About:


If you are running an earlier version of Expression Blend such as V1 or V2, please do not install the .NET Framework 3.5 SP1 Beta. Instead, please wait for the final release of .NET Framework 3.5 SP1 that will be compatible with all versions of Expression Blend.

Sending us Feedback
If you have any questions or encounter other issues while running Expression Blend 2.5 on .NET Framework 3.5 SP1 Beta, please let us know by posting on our forums.


Update (13 May 2008)
There’s been some confusion around the date of this blog post- the date that it’s picking up is when we originally discovered that we’d have to do an update to Blend coinciding with the 3.5 SP1 Beta and prepared the original draft of the blog post that we’d use to communicate the issue.

The publish date was completely accidental- just a byproduct of trying to coordinate releases. Sorry about the confusion, we really weren’t trying to be sneaky at all!

Leave a Comment
  • Please add 2 and 4 and type the answer here:
  • Post
  • Yesterday I did a brief post about " WPF 3.5 & VS 2008 SP1 Beta ".  Now I follow it

  • is they are in hurry to release new software's without thinking about are previous versions are also supported or not

  • Eerder deze week brachten we een publieke betaversie uit van de komende .NET 3.5 SP1 en VS 2008 SP1.

  • Eerder deze week brachten we een publieke betaversie uit van de komende .NET 3.5 SP1 en VS 2008 SP1.

  • Eerder deze week brachten we een publieke betaversie uit van de komende .NET 3.5 SP1 en VS 2008 SP1.

  • 【原文地址】 Visual Studio 2008 and .NET Framework 3.5 Service Pack 1 Beta 【原文发表日期】 Monday, May 12, 2008 9

  • Das am 13. Mai v2008 veröffentlichte " Microsoft .NET Framework 3.5 Service pack 1 Beta " harmonisiert

  • Setting up your WPF build environment can be a tedious exercise. this weekend, I re-formatted my build

  • Web开发之改进



  • I've been and I'm  a .NET developer for past 15 years, making a living out of it. These days, I'm getting little tired of too many technologies released too quickly by MS, then they are replaced again by other technologies too often. Releasing a service pack for a RTM product is understandable. Why release a Service Pack - Beta? Why can't MS wait and do more testing by your own engineers and then release a finished Service Pack? It is not fair to make thousands of .NET developers to spend hours, to go thorough the installation, troubleshooting, blogging, and all kinds of knowledge sharing, just to use MS products to make a living. IN MY OPINION IT IS TAKING ADVANTAGE OF THE LOYAL DEVELOPERS, COMPLETELY UNFAIR.

    Has anybody thought this way?

  • Kumar:

       That is really quite impressive.  15 years ago (when you became a .NET developer) was in 1993.  Windows 3.11 was quite the rage, especially windows 3.11 for workgroups, which had (gasp) built-in networking.  The .NET framework would not even be conceived of for an additional 5 years.  It must have been difficult in those early years, developing for a platform years before it had even been specified, quite possibly in a language that didn't exist yet.

          Perhaps you ment you have been programming windows for 15 years, as have I.  I still do not see how additional access to early builds for people who want them is unfair.  I agree with you, destabalizing by build enviornment with a beta platform is not a risk I can afford right now, so I'm not participating in this beta.  Far from beeing hurt by microsoft offering public beta I don't download, I will get the additional quality in the final bits when they release.

        Software is different than 15 years ago.  Frequent releases are now the rule -- as microsoft painfully discovered in the delayed vista release.  New technologies will continue to come out, its called innovation.  Pick the ones you need, discard the rest.

    At any rate I do not see how more (FREE by the way) options than we previously had could be considered taking advantage of anyone.

  • Earlier today we shipped a public beta of our upcoming .NET 3.5 SP1 and VS 2008 SP1 releases. These servicing

Page 2 of 2 (27 items) 12