Postprocessor IDE for SolidCAM

Write and maintain GPPL postprocessors for SolidCAM and InventorCAM in Visual Studio Code. Community provides completion, navigation, diagnostics, and formatting for individual .gpp files.
Website · Documentation · Install Community

What you can do
- Write with context. Semantic highlighting, hover descriptions, signature help, and completion for your symbols, 1633 system variables, 199 system procedures, and 95 built-in functions. Editor guide. Newly recognized catalog names may have no description or confirmed type yet.
- Complete calls faster. Procedure and built-in function completion inserts argument placeholders; a selected expression can become the first argument.
- Find and fix problems. Syntax, semantic, and encoding diagnostics with Quick Fixes for supported issues, including duplicate declarations and missing block endings. Diagnostics guide.
- Navigate your code. Go to Definition, Find All References, and scope-aware Rename within a file, plus Outline, folding, snippets, and formatting.
- Use machine parameters. Recognize supported user variables from the matching
.vmid file in completion, hover, and type checking. VMID guide.
Descriptions, diagnostics, and extension UI follow VS Code's display language: English, Russian, or German.
Community and PRO
Community is free and available now. Its symbol analysis operates within the current file.
PRO is in closed beta and has not been publicly released. Project navigation and cross-file analysis are being tested with invited participants. See edition availability and comparison.
Get started
Requires Windows x64 and VS Code 1.85 or later. The language server includes its .NET runtime.
Install from the Visual Studio Marketplace, or run:
code --install-extension anzory.vscode-gppl-ide
Open a .gpp file, press Ctrl+Space for completion, F12 for a definition, or Ctrl+. on a diagnostic for available fixes.
For offline installation, download the Community VSIX from GitHub Releases and choose Extensions → … → Install from VSIX…. Follow the quick start for setup and first steps.
Color theme
Community 1.7.0 renames the bundled theme to GPPL Classic Dark (previously GPPL UltraEdit), with the same palette. Select it through Preferences: Color Theme. Its settings ID remains GPPL UltraEdit, so an existing workbench.colorTheme selection and [GPPL UltraEdit] color overrides continue to work. Keep that ID when editing settings JSON; no migration is needed.
Customize token colors
Keep your theme and adjust GPPL colors in Preferences: Open User Settings (JSON). For example, these rules distinguish the two quote styles in Community 1.7.0:
{
"editor.semanticTokenColorCustomizations": {
"rules": {
"string:gppl": "#9CDCFE",
"string.format:gppl": "#FF8000"
}
}
}
Merge the rules into your existing settings; semantic highlighting must be enabled. The highlighting guide provides the full category reference, ready-to-copy settings, TextMate fallback, and troubleshooting. Русская инструкция.
Community 1.7.0 adds separate categories for word comparisons, logic, generation braces, nb/nl, :, built-in functions, and system/user procedures. These selectors are not available in 1.6.3. In GPP mode, use :gpp; with semantic highlighting off, that mode uses the SolidCAM extension's grammar.
Keep procedure documentation in sync
Since Community 1.7.0: renaming a procedure parameter with F2 also updates its <param name="..."> attribute in the adjacent ;;; XML documentation block. The declaration, references and documentation name change together, with one Undo/Redo operation. Description text and other procedures remain unchanged.
After adding, removing or reordering parameters, place the caret in the procedure or its documentation and run SolidCAM GPPL: Synchronize Procedure Documentation from the Command Palette or editor context menu. The command adds missing <param> tags and orders them by the current signature. It preserves existing descriptions, summary and remarks; tags for removed parameters are retained after the current parameters and reported for review. It never infers a rename from parameter position. Use F2 when renaming, or review retained descriptions yourself after a manual rename.
The command updates an existing adjacent ;;; block. To create one, type ;;; on a separate line immediately above the procedure. Put each <param> element on its own ;;; line or group of lines; multiline descriptions are supported. Incomplete XML or duplicate parameter tags require correction before synchronization. The command edits the open buffer without saving or changing the file encoding; repeated synchronization is a no-op once the block matches the signature.
Check your file encoding
The default is Windows-1252. For Cyrillic postprocessors, configure Windows-1251 for both gppl.encoding and VS Code's GPPL file encoding. If text opens incorrectly, use Reopen with Encoding before saving. See the encoding guide for settings and the difference between reopening and converting a file.
The extension synchronizes the User GPPL file encoding when the project does not override gppl.encoding. Workspace and Folder settings are preserved. If an override conflicts with the language server's encoding, a warning opens the relevant settings; adjust the conflicting values manually. The server uses one encoding per VS Code window, so different Folder encodings in a multi-root workspace require separate windows or matching settings. Changing a setting does not reopen or convert an already open document.
Help and release notes
License and acknowledgements
The extension client is MIT-licensed; the language server binary is proprietary. See LICENSE.
Built with ANTLR 4, OmniSharp LSP, Serilog, and .NET. Component licenses and attribution are included in THIRD_PARTY_NOTICES.md.
Disclaimer. This is an unofficial, independently developed extension. "SolidCAM" is a registered trademark of SolidCAM Ltd. "GPPL" (General Post-Processor Language) refers to the proprietary postprocessor language used by SolidCAM products. This extension is not affiliated with, endorsed by, sponsored by, or supported by SolidCAM Ltd. All trademarks are the property of their respective owners.