APIs we should scan for in a Task analyzer
Open
Area: Analyzer
Priority:2
triaged
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 141
Description
There are several categories of API that are problematic in MSBuild tasks. Ideally we'd have a Roslyn analyzer (or something) that would ban them (from both the task and ideally the closure of things it calls).
### Things to just error on
* `Debug.Fail` and `Environment.FailFast` (kills worker node without giving time to report the error)
### Things we'd need to have a replacement for
* Current working directory
* environment
* File I/O (because of implicit CWD, but this is hard to balance)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.