Merge pull request #6729 from rainersigwald/usingtask-schema

MSBuild: UsingTask runtime/architecture requirements

Author: PRMerger15

docs/msbuild/how-to-configure-targets-and-tasks.md

@@ -109,3 +109,4 @@ The `MSBuildRuntime` and `MSBuildArchitecture` parameters provide the most flexi
 ## See also
 
 - [Configure targets and tasks](../msbuild/configuring-targets-and-tasks.md)
+- [UsingTask element](../msbuild/usingtask-element-msbuild.md)

docs/msbuild/usingtask-element-msbuild.md

@@ -46,8 +46,10 @@ Maps the task that is referenced in a [Task](../msbuild/task-element-msbuild.md)
 
 |Attribute|Description|
 |---------------|-----------------|
+|`Architecture`|Optional attribute.<br /><br /> Specifies that the task must run in a process of the specified bitness. If the current process does not satisfy the requirement, the task will be run in a task host process that does.<br /><br /> Supported values are `x86` (32-bit), `x64` (64-bit), `CurrentArchitecture`, and `*` (any architecture).|  
 |`AssemblyName`|Either the `AssemblyName` attribute or the `AssemblyFile` attribute is required.<br /><br /> The name of the assembly to load. The `AssemblyName` attribute accepts strong-named assemblies, although strong-naming is not required. Using this attribute is equivalent to loading an assembly by using the <xref:System.Reflection.Assembly.Load%2A> method in .NET.<br /><br /> You cannot use this attribute if the `AssemblyFile` attribute is used.|
 |`AssemblyFile`|Either the `AssemblyName` or the `AssemblyFile` attribute is required.<br /><br /> The file path of the assembly. This attribute accepts full paths or relative paths. Relative paths are relative to the directory of the project file or targets file where the `UsingTask` element is declared. Using this attribute is equivalent to loading an assembly by using the <xref:System.Reflection.Assembly.LoadFrom%2A> method in .NET.<br /><br /> You cannot use this attribute if the `AssemblyName` attribute is used.|
+|`Runtime`|Optional attribute.<br /><br /> Specifies that the task must run in a .NET Framework runtime of the specified version. If the current process does not satisfy the requirement, the task will be run in a task host process that does. Not supported in .NET Core MSBuild.<br /><br /> Supported values are `CLR2` (.NET Framework 3.5), `CLR4` (.NET Framework 4.7.2 or higher), `CurrentRuntime`, and `*` (any runtime).|  
 |`TaskFactory`|Optional attribute.<br /><br /> Specifies the class in the assembly that is responsible for generating instances of the specified `Task` name.  The user may also specify a `Task` as a child element that the task factory receives and uses to generate the task. The contents of the `Task` are specific to the task factory.|
 |`TaskName`|Required attribute.<br /><br /> The name of the task to reference from an assembly. If ambiguities are possible, this attribute should always specify full namespaces. If there are ambiguities, MSBuild chooses an arbitrary match, which could produce unexpected results.|
 |`Condition`|Optional attribute.<br /><br /> The condition to evaluate. For more information, see [Conditions](../msbuild/msbuild-conditions.md).|
@@ -105,5 +107,6 @@ The assembly containing the custom task is loaded when the `Task` is first used.
 ## See also
 
 - [Tasks](../msbuild/msbuild-tasks.md)
+- [How to: Configure targets and tasks](../msbuild/how-to-configure-targets-and-tasks.md)   
 - [Task reference](../msbuild/msbuild-task-reference.md)
 - [Project file schema reference](../msbuild/msbuild-project-file-schema-reference.md)