Support VS 2022 #850
Labels
bug
Something isn't working
Comments
|
For now I reverted my repository back to use VS 2019. |
|
Yes, database creation on Windows Server 2022 is currently broken (no matter which release of Visual Studio). The system libraries in the OS update change some details that CodeQL was depending upon for observing what the build process does. We have some engineers working urgently on getting it to work, but it's complicated and we have no firm ETA for a fix yet. :-( |
ahwm
added a commit
to ahwm/GodaddyWrapper.Net
that referenced
this issue
Jan 4, 2022
disabling CodeQL due to lack of .NET 6 support: github/codeql-action#757 and github/codeql-action#850
blu3mania
added a commit
to blu3mania/npp-papyrus
that referenced
this issue
Feb 22, 2022
baywet
added a commit
to microsoft/OpenAPI.NET.OData
that referenced
this issue
Feb 25, 2022
Signed-off-by: Vincent Biret <[email protected]>
2 tasks
pbatard
added a commit
to pbatard/ntfs-3g
that referenced
this issue
May 30, 2022
Also drop CodeQL for the time being, as it is still not compatible with VS2022 (github/codeql-action#850).
|
This eventually got fixed. |
ann0see
added a commit
to ann0see/jamulus
that referenced
this issue
Jun 15, 2022
Fixes: jamulussoftware#2259 Visual Studio and CodeQl now work on windows-2022 according to github/codeql-action#850
5 tasks
ann0see
added a commit
to ann0see/jamulus
that referenced
this issue
Jun 18, 2022
Fixes: jamulussoftware#2259 Visual Studio and CodeQl now work on windows-2022 according to github/codeql-action#850
pbatard
added a commit
to pbatard/rufus
that referenced
this issue
Jun 23, 2022
* Also reinstate CodeQL since github/codeql-action#850 is supposed to be fixed and add dependabot.yml. * Also fix a false Coverity warning.
pbatard
added a commit
to pbatard/rufus
that referenced
this issue
Jun 23, 2022
* Also reinstate CodeQL since github/codeql-action#850 is supposed to be fixed. * Also fix a false Coverity warning.
tuxgal
added a commit
to tuxgal/tuxlogi
that referenced
this issue
Oct 31, 2024
There is lack of CodeQL VS/Win 2022 support. Upstream Tracking bug(s): github/codeql-action#850 github/codeql-action#821
tuxgal
added a commit
to tuxgal/tuxlog
that referenced
this issue
Oct 31, 2024
…port. Upstream Tracking bug(s): github/codeql-action#850 github/codeql-action#821
tuxgal
added a commit
to tuxgal/cablemodemutil
that referenced
this issue
Oct 31, 2024
There is lack of CodeQL VS/Win 2022 support. Upstream Tracking bug(s): github/codeql-action#850 github/codeql-action#821
tuxgal
added a commit
to tuxgal/cablemodemcli
that referenced
this issue
Oct 31, 2024
There is lack of CodeQL VS/Win 2022 support. Upstream Tracking bug(s): github/codeql-action#850 github/codeql-action#821
tuxgal
added a commit
to tuxgal/prometheus_cable_modem_exporter
that referenced
this issue
Nov 1, 2024
There is lack of CodeQL VS/Win 2022 support. Upstream Tracking bug(s): github/codeql-action#850 github/codeql-action#821
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I updated one of my repositories to use VS 2022 and MSVC Tools v143 to build, and although I could use the latest "windows-2022" hosted runner to successfully build my solution, CodeQL failed. After digging around I found #821 which is the exact same issue, and from the linked support page it states that VS support is only up to 2019.
Can VS 2022 support be added? Thanks.
The text was updated successfully, but these errors were encountered: