HFDotnetEx.System.Threading.Tasks.Extensions.Ex 4.1.29

dotnet add package HFDotnetEx.System.Threading.Tasks.Extensions.Ex --version 4.1.29
                    
NuGet\Install-Package HFDotnetEx.System.Threading.Tasks.Extensions.Ex -Version 4.1.29
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="HFDotnetEx.System.Threading.Tasks.Extensions.Ex" Version="4.1.29" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="HFDotnetEx.System.Threading.Tasks.Extensions.Ex" Version="4.1.29" />
                    
Directory.Packages.props
<PackageReference Include="HFDotnetEx.System.Threading.Tasks.Extensions.Ex" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add HFDotnetEx.System.Threading.Tasks.Extensions.Ex --version 4.1.29
                    
#r "nuget: HFDotnetEx.System.Threading.Tasks.Extensions.Ex, 4.1.29"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package HFDotnetEx.System.Threading.Tasks.Extensions.Ex@4.1.29
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=HFDotnetEx.System.Threading.Tasks.Extensions.Ex&version=4.1.29
                    
Install as a Cake Addin
#tool nuget:?package=HFDotnetEx.System.Threading.Tasks.Extensions.Ex&version=4.1.29
                    
Install as a Cake Tool

DotnetEx4

DotnetEx4 is organized in a dotnet/runtime-inspired layout so legacy .NET Framework backports, modern targets, tests, and NuGet packaging have clear ownership and minimal duplicated MSBuild configuration.

Repository layout

  • Directory.Build.props / Directory.Build.targets — root repository controller pair, like dotnet/runtime
  • global.json — repository SDK selection
  • eng/ — central build, target, version, dependency, signing, validation and NuGet controllers
  • src/corelib/HFDotnetEx.HFExtensions, the mscorlib/System.Private.CoreLib compatibility layer
  • src/libraries/ — product libraries and runtime/framework backports
  • src/tools/ — repository tools
  • src/shared/ — shared .shproj / .projitems source
  • tests/ — isolated test projects; target-map only, never NuGet packages
  • samples/ — isolated demos; target-map only, never NuGet packages
  • DotnetEx4.slnx — canonical solution
  • DOTNETEX4_PROJECT_MAP.txt — complete architecture and agent operating manual

Central-control rule

One setting has one owner. Repository-wide C# 14/default paths/common symbols live in root Directory.Build.props; framework profiles live in eng/TargetFrameworks.props; project registration in eng/Projects.props; dependency routing in eng/Dependencies.props; versions in eng/Versions.props; package selection/IDs in eng/NuGet.props; and signing in eng/Signing.props.

The root Directory.Build.* pair is deliberately small. Production folders (src/corelib, src/libraries, src/tools) have scoped Directory.Build.* files that explicitly import the root pair and then the production eng/Build.* chain. Tests and samples have no local Directory.Build.*; they inherit only the safe root defaults/target map and never production signing/NuGet/dependency controllers.

Source ownership

For every exact API/target, prefer: native runtime/framework → official Microsoft NuGet package → DotnetEx backport. Never allow duplicate owners for the same API on the same target.

NuGet

The current release version is 4.1.29, controlled only by eng/Versions.props. eng/NuGet.props is the only package allow-list. It currently contains 24 production packages; tests and samples are excluded.

Before editing

Read DOTNETEX4_PROJECT_MAP.txt. It explains every controller, target profile, production project, package identity, special ownership boundary, test/sample rule, and the exact procedure for adding a new project.

Product Compatible and additional computed target framework versions.
.NET Framework net20 is compatible.  net30 is compatible.  net35 is compatible.  net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on HFDotnetEx.System.Threading.Tasks.Extensions.Ex:

Package Downloads
HFDotnetEx.System.Memory.Ex

System.Memory compatibility/backport package for legacy .NET Framework targets before the exact official Microsoft package boundary used by DotnetEx.

HFDotnetEx.Microsoft.Bcl.AsyncInterfaces.Ex

Microsoft.Bcl.AsyncInterfaces compatibility/backport package for legacy .NET Framework targets that do not have an exact supported Microsoft package asset in the DotnetEx target map.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.1.29 112 9/11/2026
4.1.7 121 9/8/2026