Repository navigation
Getting PiCode
Two ways in, for two different people.
Go to Releases and take the file for your platform:
| File | What it is |
|---|---|
...-setup.exe |
Windows installer (Inno Setup) |
...<version>.zip |
Windows portable — unzip, run PiCode.exe
|
SHA256SUMS.txt |
checksums of everything above |
Verify the checksum before the first run. Windows binaries are not code-signed yet, so SmartScreen warns once (More info → Run anyway). That is expected, not tampering. Signing is being set up through the SignPath Foundation; the policy is in the repository README.
On the first run PiCode creates a data/ folder next to the executable:
user data, extensions, sessions, cache and the Pi profile.
Nothing is written to %APPDATA%.
- Delete
data/→ you get a clean PiCode. - Copy it → your whole PiCode moves to another machine.
No profile travels inside the archive itself: fresh ZIP, fresh start. Continue with First Run and the Wizard.
Three channels share the same code, each on its own branch:
| Channel | Branch | Version looks like | For |
|---|---|---|---|
| Stable | master |
0.5.2 |
everyday use |
| Beta | beta |
0.5.2-beta |
early access |
| Experimental | experimental |
0.5.2-experimental |
freshest work |
Each channel installs beside the others, with its own profile, and has its own update feed: the editor offers the update when one appears (see Updates and Hotfixes). Switching channel means installing that channel's release; the editor follows the feed of the build you run.
The repository carries PiCode's own source tree: the repository itself is the VS Code-derived editor with every PiCode change committed as code. Nothing is downloaded and nothing is patched — clone and compile:
./build/build.sh # full chain, dependencies installed once
./build/build.sh -o # fast check — nothing installed or compiledReleases are produced by exactly this build: what you compile is what ships. The full dependency list, the five build phases and the GUI alternative are in Building PiCode. If you plan to contribute, read CONTRIBUTING.md first — it names the rules that have burned the project before.
| Symptom | Meaning |
|---|---|
| SmartScreen warning | the binary is not signed yet; verify the checksum, run anyway |
| No update is offered | see Updates and Hotfixes |
| The model list is empty | no provider connected yet — connect one in setup or in Pi Inside |
| A theme cannot install | it exists only on the Microsoft Marketplace; PiCode installs from Open VSX |
More in Troubleshooting.
Next: First Run and the Wizard