Incremental compilation is unsafe when compilation relies on tools with potential side effects (tools that can cause data races or modify the state of other projects that have been deemed safe to skip compilation. Or tools that integrate timestamps or GUIDs into the build output).
The presence of such cases will turn off incremental compilation.
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.
-
[PATH probing]: Resolving tool names from PATH is problematic. First, we cannot detect when PATH tools change (which would to trigger re-compilation of sources). Second, it adds machine specific dependencies which would cause the build to succeed on some machines and fail on others. Consider using NuGet packages instead of PATH resolved tools. Thus there would be no machine specific dependencies and we would be able track when NuGet packages change and therefore trigger re-compilation.
-
[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 not incremental because the
--no-incrementalflag was used. Remove this flag to enable incremental compilation.