Microsoft C/C++ Extension appears to no longer support unofficial forks of VS Code
As of the latest update of Microsoft's C/C++ extension (v1.24.5, released April 3, 2025), use on non-Microsoft products appears to have been blocked. Upon initializing the extension, I get the follow error notification: <img width="283" alt="Image" src="https://github.com/user-attachments/assets/5c77eaa9-8e05-41e1-844a-a528b171e72e" /> Text: > The C/C++ extension may be used only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services to develop and test your applications. I realize this is not a fault of VSCodium, but I figured I would bring this to the dev team's attention since this seems like a pretty severe issue and haven't seen any other mention of it in this repo or the repo of the C/C++ extension. I found one other recent mention of this issue on another project: https://github.com/getcursor/cursor/issues/2976. Might also be related to the following Discussion, but it was created about a week ago, and this new issue has only presented itself (to me) today (April 4th) after the extension was updated: https://github.com/VSCodium/vscodium/discussions/2286. For now, I have downgraded to the previous version (v1.23.6) and disabled Auto Update. Hopefully something can be done to remedy this. VSCodium version: 1.96.4.25017 Platform: Windows 10 (22H2, 19045.5608)
Posted by ImagineBaggins on Apr 4, 2025, 5:31 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Microsoft C/C++ Extension appears to no longer support unofficial forks of VS Code
As of the latest update of Microsoft's C/C++ extension (v1.24.5, released April 3, 2025), use on non-Microsoft products appears to have been blocked. Upon initializing the extension, I get the follow error notification: <img width="283" alt="Image" src="https://github.com/user-attachments/assets/5c77eaa9-8e05-41e1-844a-a528b171e72e" /> Text: > The C/C++ extension may be used only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services to develop and test your applications. I realize this is not a fault of VSCodium, but I figured I would bring this to the dev team's attention since this seems like a pretty severe issue and haven't seen any other mention of it in this repo or the repo of the C/C++ extension. I found one other recent mention of this issue on another project: https://github.com/getcursor/cursor/issues/2976. Might also be related to the following Discussion, but it was created about a week ago, and this new issue has only presented itself (to me) today (April 4th) after the extension was updated: https://github.com/VSCodium/vscodium/discussions/2286. For now, I have downgraded to the previous version (v1.23.6) and disabled Auto Update. Hopefully something can be done to remedy this. VSCodium version: 1.96.4.25017 Platform: Windows 10 (22H2, 19045.5608)
Comments (0)
No comments yet. Start the discussion.