CLI tool
roslynpad/roslynpad avatar
roslynpad/roslynpad

RoslynPad compiles with the .NET SDK you already have, and its feature list is eight empty headings

Cross-platform C# editor based on Roslyn

2,834 stars393 forksC#MIT

At a glance

What is it?
RoslynPad is a cross platform C# editor built on Roslyn for compilation and on Morgania, an Avalonia editor derived from Microsoft's vs-editor-api, for the editing surface. The page is short, and the two facts it states most clearly are that you must install a supported .NET SDK separately, and that the feature section lists Completion, Signature Help, Quick Info, Diagnostics, Code Fixes, NuGet Packages, Document Management and Dump Results without describing any of them.
Who is it for?
RoslynPad fits a specific habit: opening a scratch file, compiling it, and reading what came back, without launching a full IDE. Two things to check before you rely on it.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
Mainly C#, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • roslynpad/roslynpad2,834 ★ · +10
Star history
Repository2026-10-042026-11-15
roslynpad/roslynpad2.8k2.8k

10 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The feature section is eight headings with nothing under them

The features section is the clearest example of a page describing intentions rather than behaviour. It contains eight subheadings and no prose under any of them: Completion, Signature Help, Quick Info, Diagnostics, Code Fixes, NuGet Packages, Document Management and Dump Results. Each name describes a capability an editor of this kind would be expected to have, and none of them is explained, qualified or dated. The implication for anyone evaluating the project is that the feature surface has to be established from the source or from running the application, because the page will not tell you which of the eight are finished, which are partial, or which are older than the current release. The rest of the page is similarly economical: a title, a one line description, an install table, a packages pointer, a build section and that feature list.

The SDK is a prerequisite, not an implementation detail

One line in the install section carries more weight than the rest of the page. You must also install a supported .NET SDK to allow RoslynPad to compile programs. That is the whole architecture in a sentence: this is a tool that compiles, so it needs a compiler toolchain present on the machine, and the application does not bring one. Two consequences follow. The first is that what your snippets can use depends on which SDK you have installed, and on its version, since the page says a supported SDK without naming versions or a floor. The second is that installation is a two step affair on every platform, which is why the install table lists four sources for the application itself and the SDK requirement sits above it as a separate line rather than being bundled into any of those sources.

Four sources for the application, one per platform convention

The install table is where the page is most concrete. Four routes are offered, and they cover the three major desktop package managers plus direct downloads:

bash
winget install --id RoslynPad.RoslynPad
bash
brew install --cask roslynpad

Alongside those, the Microsoft Store entry and a link to the latest GitHub releases. The Homebrew cask is the interesting one for a cross platform .NET desktop application, since casks are how the brew project handles things that are not library packages, and the Microsoft Store entry covers the Windows path without an installer of your own. Nothing on the page states which of these receives updates first, so a user who wants the newest build and does not want a store account has the GitHub releases as the direct route.

The editing surface is Morgania, an Avalonia port of vs-editor-api

The first line of the page credits two things rather than one. RoslynPad is powered by Roslyn, which is the C# compiler itself and therefore the part that makes compiling possible, and by what it calls the Morgania editor, described as an Avalonia editor based on the vs-editor-api repository from Microsoft. That is a meaningful dependency arrangement: the editor surface is a port of a Visual Studio editor component onto Avalonia, which is what makes a single cross platform binary possible rather than a native Windows application. It also means the visual behaviour of the editor is not entirely this repository's to decide. The tree is consistent with that: there is a .gitmodules file and a vendor directory at the top level, so at least one dependency arrives as a checked in submodule rather than being restored by a package manager.

Three ways to build, and one of them is Windows only

Building from source is a short list with an asymmetry in it. The three options are a plain command:

bash
dotnet build

or Visual Studio Code with the C# extension, or Visual Studio 2026, which the page marks as Windows only. So the cross platform claim holds for the application and for two of the three build routes, with the third being the traditional Windows path. That is the expected shape for a .NET desktop project and worth stating plainly rather than discovering later. The repository layout supports the same picture: a solution file named RoslynPad.slnx in the XML form, Directory.Build.props and Directory.Build.targets for shared build behaviour, Directory.Packages.props for central package versions, a global.json pinning the SDK, and separate src, tests, deploy and docs directories.

Version numbers follow the Visual Studio year scheme and lag the branch

The release list explains the versioning, if you read it against the dates. There is 21.1 published on 7 June 2026, 22 on 20 July 2026 and 22.1 on 4 August 2026. The major number is not a calendar year of release, since two of these shipped in 2026, which is the pattern used by tools that align their versions with Visual Studio rather than with their own release dates. Two practical points follow. The last commit on the default branch is dated 19 September 2026, about six weeks after the 22.1 release, so the branch is ahead of the newest tag and the binary you get from a package manager is not the code you read. And because the scheme is year based, the numbers do not tell you anything about recency on their own; the dates do.

A short page, a vendored dependency, and an agent instruction file

The top level listing shows more process than documentation. Alongside the usual editor and ignore files there is a vendor directory paired with the submodule file, a nuget.config written in lower case while the Directory.Build files use capitalised names, a dotfiles directory for editor settings, and a .claude directory next to a CLAUDE.md file at the root. There is also a CODE_OF_CONDUCT.md and a CONTRIBUTING.md, a LICENSE file, and an .editorconfig and .gitattributes. Taken with the page itself, which runs to roughly a hundred words before the feature headings, the pattern is a project that expects you to read the repository rather than the readme: the documentation lives in docs, the packages guidance is one link into docs/packages, and the specifics that would normally appear in prose are simply not there.

Editorial conclusion

RoslynPad fits a specific habit: opening a scratch file, compiling it, and reading what came back, without launching a full IDE. Two things to check before you rely on it. It compiles rather than interprets, so a supported .NET SDK has to be installed on the machine and its version decides what your snippets can use, which makes the editor's reach a property of your toolchain. And the page documents almost nothing about what the editor does, so treat the eight feature headings as a list of intentions rather than a specification, and check the source or the application itself for whether a given capability is finished. For anything longer than a snippet, this is not a replacement for an IDE.

Frequently asked questions

What does RoslynPad need installed besides the application itself?

A supported .NET SDK, installed separately. The page states you must also install one to allow RoslynPad to compile programs, which means the application depends on a toolchain already present on the machine and does not bundle one.

How do I install RoslynPad?

Four sources are listed: the latest GitHub releases, the Microsoft Store, winget with winget install --id RoslynPad.RoslynPad, and Homebrew with brew install --cask roslynpad. Whichever you choose, a supported .NET SDK is a separate requirement.

Which editor does RoslynPad use for its editing surface?

Morgania, described as an Avalonia editor based on Microsoft's vs-editor-api repository, with Roslyn providing compilation. The repository also carries a vendor directory alongside a submodule file, so at least one dependency arrives as a checked in submodule.

How do I build RoslynPad from source?

With dotnet build, with Visual Studio Code and the C# extension, or with Visual Studio 2026, which the page marks as Windows only. The repository uses an XML solution file, shared build properties and targets, central package version management and a global.json that pins the SDK.

Which features does RoslynPad document?

Eight names and no descriptions: Completion, Signature Help, Quick Info, Diagnostics, Code Fixes, NuGet Packages, Document Management and Dump Results. The page does not say which are complete, which are partial, or when any of them last changed.

How is RoslynPad versioned?

With a year style major number rather than a release date: 21.1 on 7 June 2026, 22 on 20 July 2026 and 22.1 on 4 August 2026. The last commit on the main branch is dated 19 September 2026, so the branch is roughly six weeks ahead of the newest release.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. roslynpad/roslynpad on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/roslynpad-roslynpad.svg)](https://hysenlabs.com/projects/roslynpad-roslynpad)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/roslynpad-roslynpad.svg)](https://hysenlabs.com/projects/roslynpad-roslynpad)

Was this useful?