Task hosts should set TaskEnvironment instead of relying on task defaults
Open
Area: Tasks
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 141
Description
Currently, task hosts rely on individual tasks to provide a default `TaskEnvironment`. The out-of-proc task host never assigns `TaskEnvironment` on `IMultiThreadableTask` instances. Today this only works because our built-in tasks initialize the property to `TaskEnvironment.Fallback` themselves. To improve reliability the task host should be responsible for initializing and setting the `TaskEnvironment`.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.