You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add runtime mismatch validation when Runtime is explicitly specified in custom task (#12642)
### Context
Currently, in order to have Runtime="Net" executed out-of-proc, you must
explicitly specify TaskFactory="TaskHostFactory" in the UsingTask
element.
### Changes Made
Added runtime mismatch validation when Runtime is explicitly specified
to omit TaskFactory specification in UsingTask.
### Regression
No
### Risks
Low — validation logic only affects cases where Runtime is explicitly
set.
### Testing
Added a dedicated test.
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Rainer Sigwald <raines@microsoft.com>
Co-authored-by: Chet Husk <chusk3@gmail.com>
/// Determine whether an assembly is likely to be used out of process and thus loaded with a <see cref="MetadataLoadContext"/>.
385
+
/// </summary>
386
+
/// <param name="useTaskHost">Task Host Parameter was specified explicitly in XML or through environment variable.</param>
387
+
/// <param name="taskHostParamsMatchCurrentProc">The parameter defines if Runtime/Architecture explicitly defined in XML match current process.</param>
0 commit comments