Skip to main content

.NET Framework 4 Platform Update

Last week Microsoft announced the release of Microsoft .NET Framework 4 Platform Update 1. This 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 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.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more