MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration (Runtime="{1}", Architecture="{2}") does not match the identity specified by the task invocation (MSBuildRuntime="{3}", MSBuildArchitecture="{4}").
MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, ...
MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. ...
MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import ...
MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild ...
MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration ...
MSB4215: The "{0}" task could not be loaded. "{1}" is an invalid value for the task host parameter "{2}". Valid values are: ...
MSB4216: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture ...
MSB4217: Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory ...
MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches ...