Share via

Microsoft .NET Framework 4 Platform Update 1

  • Article

The Microsoft .NET Framework 4 Platform Update 1 released today, 4/18/2011.

The Microsoft .NET Framework 4 Platform Update 1 is a platform update that is a set of new features that provides additional functionality for top customer requests and important scenarios.

The features that are enabled in this update are:

Windows Workflow Foundation (WF)

The Microsoft .NET Platform Update 1 consists of three packages:

  • Microsoft .NET Framework 4 Platform Update 1 (KB2478063)
    • This package contains the runtime files for the platform update. This package must be deployed on systems where applications that target the platform update are deployed.
  • Multi-Targeting Pack for Microsoft .NET Framework 4 Platform Update 1 (KB2495638)
    • This package contains reference assemblies and intellisense files for the platform update. This package is installed as part of the next package.
  • Microsoft .NET Framework 4 Platform Update 1 – Design-time Package for Visual Studio 2010 SP1 (KB2495593)
    • This package installs the previous two packages and configures Visual Studio 2010 SP1 with new .NET Framework targeting profiles, intellisense, and adds the state machine activities to the toolbox.

To develop workflow applications in Visual Studio 2010 SP1 that target the new Platform Update 1 functionality, the Microsoft .NET Framework 4 Platform Update 1 – Design-time Package for Visual Studio 2010 SP1 (KB2495593) must be installed. Once it is installed, the .NET Framework 4 Platform Update 1 (KB2478063) profile can be chosen when creating a new .NET application.

There are two new profiles added to Visual Studio when the Design-time Package for Visual Studio 2010 SP1 (KB2495593) is installed.

  •  .NET Framework 4 Platform Update 1 (KB2478063)
  •  .NET Framework 4 Client Profile Platform Update 1 (KB2478063)

When a new project is created with the platform update profile selected, the .NET Framework 4 Client Profile Platform Update 1 (KB2478063) is used. The .NET Framework 4 Platform Update 1 (KB2478063) profile builds on the .NET Framework 4 profile, and the .NET Framework 4 Client Profile Platform Update 1 (KB2478063) profile builds on the .NET Framework 4 Client Profile. The .NET Framework 4 Client Profile is a subset of the .NET Framework 4 that is optimized for client applications. For more information, see .NET Framework Client Profile.

To choose either profile or change the profile after a project has been created, right-click the project in Solution Explorer, choose Properties, and select the desired profile from the Target framework drop-down.

When either of these profiles is selected, the features in the platform update are available and the State Machine activities are available in the Toolbox.

To configure .NET Framework 4 Platform Update 1 on computers with Visual Studio 2010 SP1 that are going to be used to develop applications that target the functionality in the platform update, install Microsoft .NET Framework 4 Platform Update 1 – Design-time Package for Visual Studio 2010 SP1 (KB2495593).

To configure a computer on which applications that target the .NET Framework 4 Platform Update 1 are to be deployed, deploy Microsoft .NET Framework 4 Platform Update 1 (KB2478063) and the appropriate version of the .NET Framework 4.

For information on how to use the new state machine functionality in .NET Framework 4 Platform Update 1, see:

Comments

  • Anonymous
    April 18, 2011
    The comment has been removed

  • Anonymous
    April 19, 2011
    Thank you Fredrik, links are fixed.

  • Anonymous
    April 19, 2011
    The comment has been removed

  • Anonymous
    April 19, 2011
    Note that if you set the .NET Framework launch condition of your setup/deployment project to be the Platform Update 1 version of .NET, the setup.exe insists that you don't have it (even if you do).

  • Anonymous
    April 19, 2011
    Hi Jeff, I am leaving up these comments in case other folks chime in, but we have taken the discussion offline and I will post an update to the blog once we get this figured out.

  • Anonymous
    April 20, 2011
    connect.microsoft.com/.../net-4-platform-update-1-the-splashscreen-build-action-is-not-supported-in-the-selected-target-framework

  • Anonymous
    April 21, 2011
    Are there any plans to push out this, particularly the runtime update, via Microsoft Update?

  • Anonymous
    April 22, 2011
    Any update on the ADO.NET Activity Packs?

  • Anonymous
    April 25, 2011
    Hi Joseph, WF team currently is actively working on the ADO.net activities. Once they are ready, we will ship it out to our customers with a proper release vehicle.  We will send out an update once we have a release planned locked,. Thanks!

  • Anonymous
    April 27, 2011
    Notre, there are currently no plans to push out the Platform Update 1 on Windows Update. We currently only push out major Service Packs, MSRC's and broadly applicable fixes though Windows Update.

  • Anonymous
    May 05, 2011
    Few questions: is it mainly for WF? Or it make sense also for WCF Ria development? If I do WF with this Platform Update, can i use this WF in Sharepoint?

  • Anonymous
    May 11, 2011
    Is the base .NET framework 4.0 being pushed out on Windows Update? We're trying to decide whether to upgrade our app from 3.5 to 4.0 and this is one consideration (i.e. if you are pushing it out then more people would have it already so we should upgrade.) Thanks, - Dan

  • Anonymous
    May 17, 2011
    The comment has been removed

  • Anonymous
    May 17, 2011
    LOL - the name is pretty... um... interesting.  The actual version number is 4.0.1

  • Anonymous
    May 17, 2011
    Amen, Allen. What is up with this moronic versoning scheme? At least 4.1 or 4.0.1 means something...

  • Anonymous
    May 17, 2011
    As Ron mentioned the name is.. uhm.. a bit odd.  Maybe you can explain to us why MS has decided to forgo normal naming?

  • Anonymous
    May 17, 2011
    I can't explain it.  I wasn't there when they made this decision.  

  • Anonymous
    May 18, 2011
    The comment has been removed

  • Anonymous
    May 18, 2011
    The comment has been removed

  • Anonymous
    May 18, 2011
    Haven't you learned anything from the 3.0/3.5/3.5SP1 debacle. Just grow up... and go learn something before you dump these poor standards on those that have real software to write and support! If you want to show us you respect your customers, fix this disparity, and fix it properly.

  • Anonymous
    May 18, 2011
    The comment has been removed

  • Anonymous
    May 18, 2011
    Why is this being announced and described on someones personal blog? A blog for Scot's sake! Why not somewjere proper? You'll only be announcing things on Twitter next. (And don't get me started on the cretinous name it has been given)

  • Anonymous
    May 22, 2011
    Seriously.  Fix the version name.  And ditch the person who suggested it.  Platform Update?  Really?

  • Anonymous
    May 25, 2011
    Is it april fools? How many minor non-backwards-compatible versions are you planning to release between .NET 4.0 and 5.0?

  • Anonymous
    May 25, 2011
    I know the name be a little strange but this release is backward compatible. There will be more platform updates (don't know how many) who knows maybe there is a better name out there.

  • Anonymous
    May 27, 2011
    Hey there, can't seem to get the new State Machine related activities to show up in the Toolbox. Got VS2010, SP1 and VS10SP1-KB2495593.exe applied. Switched the version in project's settings. Once I manually added <StateMachine> and <State> into the xaml file, it shows in the designer and compiles. But the toolbox still doesn't have those. Any ideas?

  • Anonymous
    May 27, 2011
    StateMachine should show up in the toolbox when you open the Workflow Designer with a project that is using Platform Update 1 as the target framework.  If this is not happening you may want to reapply the Platform Update 1 patch.

  • Anonymous
    June 19, 2011
    Hi, I have installed the Plaform update 1 on my development machine and it worked perfectly. Then I installed the Runtime update to our QA server (Win 2008 R2) and deployed my WF Service project tagged with targetFramework="4.0.1". When I access the service, I get the error: " The 'targetFramework' attribute in the <compilation> element of the Web.config file is used only to target version 4.0 and later of the .NET Framework (for example, '<compilation targetFramework="4.0">'). The 'targetFramework' attribute currently references a version that is later than the installed version of the .NET Framework. Specify a valid target version of the .NET Framework, or install the required version of the .NET Framework." There's not much resource about this online so not sure where to go from here. I have tried to re-install the update and even restart the server, to no avail. At this point, I cannot really start using the state machine feature, which is sad. Thanks Patrick

  • Anonymous
    June 20, 2011
    The composite state was removed from new state machine?

  • Anonymous
    June 20, 2011
    Patrick, this is addressed in .NET Framework 4 update: support.microsoft.com/.../2468871. See issue 9 of the KB article.

  • Anonymous
    July 03, 2011
    I downloaded the service pack update VS10SP1-KB2495593, so I could go through the StateMachine tutorial. Now when I try to open Visual Studio Pro 2010 I get  the generic "Microsoft Studio has encountered a problem..." I tried repairing, removing and uninstalling, and re installing. I am a 30 trial install. Any suggestions.

  • Anonymous
    July 04, 2011
    Never mind :D