mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Update addressing-incremental-compilation-warnings.md

Browse source
This commit is contained in:
Mihai Codoban 2016-01-07 12:39:56 -08:00
parent 1e1a0a8644
commit d810689fdb
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Documentation/addressing-incremental-compilation-warnings.md
View file

@ -5,7 +5,7 @@ Incremental compilation is unsafe when compilation relies on tools with potentia
The presence of such cases will turn off incremental compilation.
Warning codes for project structures that are unsafe:
The following represent warning codes printed by CLI when the project structure is unsafe for incremental build and advice on how to address them:
- __[Pre / Post scripts]__: Scripts that run before and after each compiler invocation can introduce side effects that could cause incremental compilation to output corrupt builds (not building when it should have built) or to over-build. Consider modifying the project structure to run these scripts before / after the entire compile process, not between compiler invocations.
@ -14,4 +14,4 @@ Warning codes for project structures that are unsafe:
- __[Unknown Compiler]__: csc, vbc, and fsc have known side effects (which files and directories they read, write, and what they are not reading/writing).
We don’t know this for other compilers. So we choose to be safe and disable incremental compilation for now. We are planning to enable specification of tool side effects in a future version, so that they can participate in incremental compilation as well.
- __[Forced Unsafe]__: The build was marked unsafe using the `--force-incremental-unsafe` flag. Remove this flag to enable incremental compilation.
- __[Forced Unsafe]__: The build was marked unsafe using the `--force-incremental-unsafe` flag. Remove this flag to enable incremental compilation.