publish-extensions
omnisharp-vscode
publish-extensions | omnisharp-vscode | |
---|---|---|
8 | 65 | |
221 | 2,592 | |
- | - | |
8.3 | 9.0 | |
1 day ago | 11 months ago | |
JavaScript | TypeScript | |
Eclipse Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
publish-extensions
-
VS Code – What's the deal with the telemetry?
The biggest caveat would be to be aware of the default connexion to an alternative extension store, https://open-vsx.org, instead of Microsoft's own store, which does not have all the extensions the official store has. But that's less and less an issue, thanks to projects such as https://github.com/open-vsx/publish-extensions. In the worst case, I just manually `git clone`d the desired extension in my local extension folder. Nothing to complain about otherwise
-
VSCodium – Free/Libre Open Source Software Binaries of VS Code
Hey folks, Geoff here from Gitpod. Very please to see there continues to be interest in open (and FOSS) software development tooling. VSCodium uses the OpenVSX registry (which Gitpod folks created) because the VS Market place is proprietary and can only be connected to from offical Visual Studio branded products.
If you can't find an extension when using VSCodium then please send a pull-request to this repository https://github.com/open-vsx/publish-extensions with the identifier and that will help grow the ecosystem of open tooling.
ICMYI - We blogged more about this over at https://www.gitpod.io/blog/openvscode-server-launch, https://www.gitpod.io/blog/cloud-ide-history and https://www.gitpod.io/blog/open-vsx.
-
VS Code or VS Codium - Which should I use?
Create a pull request to this repository to have the @open-vsx service account publish the extensions for you. It appears that they run a batch job to keep them up-to-date.
-
How to code, build, and deploy from an iPad using Gitlab and Gitpod
Geoff here from Gitpod. Solid write up and overview here. Some minor clarifications and helpful pointers!
There’s a community WIP pull request open right now to add Gitea support.
The visual studio marketplace is proprietary (by design) and as such we created OpenVSX for the open source ecosystem then gifted it to the eclipse foundation. If you see something not in OpenVSX send the pull request here https://github.com/open-vsx/publish-extensions
And, finally, Open source communities are eligible for complimentary plan upgrades to unlimited hours. https://www.gitpod.io/blog/gitpod-for-opensource
-
Reflections on Software Development from Anywhere on an iPad
Send a PR to https://github.com/open-vsx/publish-extensions
> One goal of Open VSX is to have extension maintainers publish their extensions according to the documentation. However, you may be missing specific extensions that have not been published by their maintainers: either they are not willing to do it, or they haven't found time to do it, or simply they haven't heard about Open VSX yet. Though the preferred solution for such a situation is to convince the maintainers to start publishing themselves, you can add the extensions here to have them published by our CI workflow.
-
GitHub Codespaces is now available for everyone on GitHub Teams and GitHub Enterprise Cloud
👋🧡 Geoff from Gitpod here. Thanks for your support. OpenVSX was created by Gitpod/TypeFox and gifted to the Eclipse Foundation to resolve the problem that the Visual Studio Marketplace is proprietary. Extensions can be configured to automatically be published via sending a pull-request to https://github.com/open-vsx/publish-extensions
-
Settings Sync error
The auto-publishing of the extension is failing, due to a misconfiguration of versions in it's package.json.
-
FLOSS version of VSCode and the extensions gallery
My third point addresses the FLOSS extensions not yet available on Open VSX. These can usually be added fairly easily via open-vsx/publish-extensions, or by asking the extension author to publish to Open VSX themselves. I believe this mindset is the only way in which FLOSS distributions of VS Code can ever be a viable alternative to Visual Studio Code.
omnisharp-vscode
- Microsoft is going to release new open-source vscode extension and C# language server to replace omnisharp
-
Visual Studio for Mac Roadmap?
They announced a year ago they are working on better C# support in VSCode https://github.com/omnisharp/omnisharp-vscode/issues/5276
- How to Setup VSCode for C# Programming In Less Than 3 Minutes (From a Microsoft Software Engineer)
-
Duda carrera: C#/.NET vs. Node/Express
OmniSharp (soporte de C# en VS Code): Licencia MIT
-
Microsoft eyes partnership with Firefox to make Bing its primary search engine
Let me try to find that post. It's basically the drama around this
-
MSFT is forcing Outlook and Teams to open links in Edge and IT admins are angry
> They did a wonderful job with C# and .NET Core.
And VSCode. One thing all three have in common is that they are all FREE to use--they don't make Microsoft any money directly.
And, for the segment of the developer tools market that wrangles C# code, if VSCode gets too good, it becomes a threat to a cash cow: Visual Studio.
Start here: https://github.com/OmniSharp/omnisharp-vscode/issues/5276#is...
-
Bug? - VSCode set to english but only the console's bugs are in german.
Sounds like this issue https://github.com/OmniSharp/omnisharp-vscode/issues/2513
- How do I change the language of error hints to english?
-
What is .NET, and why should you choose it? - Microsoft DevBlog
Open source. OP is referencing a decision Microsoft made last year to include some closed-source components, in particular the debugger from Visual Studio, in the default C# extension for Visual Studio Code. There is a Samsung-provided open source debugger available if you absolutely require it, but the closed source stuff doesn't have any usage restrictions afaik.
What are some alternatives?
openvsx - An open-source registry for VS Code extensions
format - Home for the dotnet-format command
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
open-vsx.org - Source of open-vsx.org
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
Code-Server - VS Code in the browser
netcoredbg - NetCoreDbg is a managed code debugger with MI interface for CoreCLR.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
Visual Studio Code - Visual Studio Code
publish-vscode-extension - GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.
micro-editor - A modern and intuitive terminal-based text editor