Skip to content

Commit b3aff6c

Browse files
authored
Update troubleshooting-the-codeql-workflow.md (#23629)
1 parent a840d2b commit b3aff6c

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -110,13 +110,13 @@ If your workflow fails with an error `No source code was seen during the build`
110110
* Building using a distributed build system external to GitHub Actions, using a daemon process.
111111
* {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
112112

113-
For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
113+
For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code.
114114

115115
For example, the following configuration for C# will pass the flag during the first build step.
116116

117117
``` yaml
118118
- run: |
119-
dotnet build /p:UseSharedCompilation=false
119+
dotnet build /p:UseSharedCompilation=false
120120
```
121121

122122
If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.

0 commit comments

Comments
 (0)