A cross-platform C# editor and REPL built on Roslyn for real-time code execution and analysis.
RoslynPad is a cross-platform desktop application that functions as a C# editor and REPL environment. It uses the Roslyn compiler platform to provide real-time code analysis, completion, and execution, allowing developers to quickly test and prototype C# code snippets. It solves the need for a lightweight, interactive tool for C# development outside of full-fledged IDEs.
C# developers, educators, and learners who need a fast, interactive environment for testing code, experimenting with language features, or teaching C# concepts without launching Visual Studio or another heavy IDE.
Developers choose RoslynPad for its speed, simplicity, and deep integration with Roslyn, offering IDE-like features such as diagnostics and code fixes in a minimal, cross-platform package. It's uniquely positioned as a dedicated C# REPL tool with rich editing capabilities.
A cross-platform C# editor based on Roslyn and AvalonEdit
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses the Roslyn compiler for accurate code completion, signature help, and real-time diagnostics, as evidenced by the feature screenshots in the README showing instant error highlighting and fixes.
Runs consistently on Windows, macOS, and Linux with installation options via GitHub releases, Microsoft Store, and winget, making it widely accessible.
Designed for speed and simplicity, prioritizing minimal overhead for quick code execution and prototyping, as stated in its philosophy.
Integrates Roslyn's code analysis to suggest and apply fixes for common issues directly in the editor, enhancing productivity without full IDE bloat.
Requires a separate .NET SDK installation to compile programs, adding setup steps and potential compatibility issues, as highlighted in the README's installation notes.
Focused solely on C# with no built-in support for other languages or full project management features, restricting use to prototyping and learning scenarios.
On macOS, users must manually approve the non-notarized app through system settings, as detailed in the README, creating friction for seamless adoption.