Method IntroduceParameter

Appends a parameter to a constructor by specifying its name and IType.

Appends an optional parameter (i.e. one that has a compile-time-constant default value) to a constructor by specifying its name and IType. The new parameter is added directly to the existing constructor; existing callers can omit the argument, so source compatibility is preserved. Binary compatibility is not preserved. Because the constructor count is unchanged, this overload is the right choice for dependency-injection scenarios where the container requires exactly one applicable constructor (for example, Microsoft.Extensions.DependencyInjection.ActivatorUtilities).

Appends a required parameter (i.e. one that has no default value) to a constructor by specifying its name and IType. The framework also emits a forwarding constructor: a compile-time stub with the pre-mutation signature that chains via : this(...) to the now-mutated constructor. The forwarding constructor obtains the new parameter's value from the supplied IPullStrategy (for example, UseExpression(IExpression) for a non-constant expression such as DateTime.Now, or IntroduceParameterAndPull(string?, IType?, IExpression?, IExpression?, bool, bool) to cascade a dependency into chained and derived constructors). Because the pre-mutation signature remains callable, both source and binary compatibility are preserved. This overload is the right choice when binary compatibility matters, when the default must be a non-constant expression, or when a parameterless constructor must remain callable (for example, through CreateInstance<T>() or the new() generic constraint). Pass a custom IConstructorOverloadingStrategy to scope which constructors receive a forwarding constructor, or to opt out entirely.

Appends a parameter to a constructor by specifying its name and Type.

Appends an optional parameter (i.e. one that has a compile-time-constant default value) to a constructor by specifying its name and Type. The new parameter is added directly to the existing constructor; existing callers can omit the argument, so source compatibility is preserved. Binary compatibility is not preserved. Because the constructor count is unchanged, this overload is the right choice for dependency-injection scenarios where the container requires exactly one applicable constructor (for example, Microsoft.Extensions.DependencyInjection.ActivatorUtilities).

Appends a required parameter (i.e. one that has no default value) to a constructor by specifying its name and Type. The framework also emits a forwarding constructor: a compile-time stub with the pre-mutation signature that chains via : this(...) to the now-mutated constructor. The forwarding constructor obtains the new parameter's value from the supplied IPullStrategy (for example, UseExpression(IExpression) for a non-constant expression such as DateTime.Now, or IntroduceParameterAndPull(string?, IType?, IExpression?, IExpression?, bool, bool) to cascade a dependency into chained and derived constructors). Because the pre-mutation signature remains callable, both source and binary compatibility are preserved. This overload is the right choice when binary compatibility matters, when the default must be a non-constant expression, or when a parameterless constructor must remain callable (for example, through CreateInstance<T>() or the new() generic constraint). Pass a custom IConstructorOverloadingStrategy to scope which constructors receive a forwarding constructor, or to opt out entirely.