The Packaging extension creates VSIX packages and enables publishing to the Visual Studio Marketplace.

The Packaging extension provides:

• VSIX Creation - Packages for VS Code extensions
• Version Management - Automatic version number management
• Multi-Extension Support - Package multiple extensions simultaneously
• Marketplace Publishing - Direct publishing

• Node.js installed
• vsce tool available:

  npm install -g @vscode/vsce

1. Ensure the project compiles
2. Ctrl+Shift+P → WVDS: Create VSIX Package
3. Select the extension (if multiple exist)
4. The package is created in binaries/dist/

binaries/dist/
  wvds-vscode-core-0.1.0.vsix
  wvds-vscode-build-0.1.0.vsix
  ...

The suite uses Semantic Versioning (SemVer):

MAJOR.MINOR.PATCH
  1.0.0

When packaging, the version can be automatically incremented:

1. Select „Increment Version“ in the dialog
2. Choose the part to increment (MAJOR, MINOR, PATCH)
3. The package.json is updated

For beta releases:

1.0.0-beta.1
1.0.0-rc.1

The suite consists of multiple extensions that can be packaged together.

An extension pack bundles multiple extensions:

{
  "name": "wvds-fpc-rad-suite",
  "displayName": "WvdS FPC RAD Suite",
  "extensionPack": [
    "wvds.wvds-vscode-core",
    "wvds.wvds-vscode-build",
    "wvds.wvds-vscode-projects",
    "wvds.wvds-vscode-ui-designer",
    "wvds.wvds-vscode-ui-meta",
    "wvds.wvds-vscode-ui-preview",
    "wvds.wvds-vscode-packaging"
  ]
}

Package all extensions at once:

1. WVDS: Create VSIX Package
2. Select „All Extensions“
3. All packages are created

1. Azure DevOps Organization - For publisher account
2. Personal Access Token (PAT) - With Marketplace permissions
3. Publisher ID - Registered at marketplace.visualstudio.com

1. Visit marketplace.visualstudio.com/manage
2. Create a publisher
3. Note the Publisher ID

1. Visit dev.azure.com
2. User Settings → Personal Access Tokens
3. Create a token with „Marketplace (Publish)“ scope

1. WVDS: Publish Package
2. Enter the PAT (stored securely)
3. The extension is uploaded

Before publishing, the following are automatically checked:

For Marketplace publishing:

{
  "name": "wvds-vscode-core",
  "displayName": "WvdS VSCode Core",
  "description": "Central infrastructure for WvdS FPC RAD Studio",
  "version": "0.1.0",
  "publisher": "wvds",
  "license": "MIT",
  "icon": "images/icon.png",
  "repository": {
    "type": "git",
    "url": "https://github.com/ArmandoFilho/WvdS.FPC"
  },
  "engines": {
    "vscode": "^1.85.0"
  },
  "categories": ["Other"],
  "keywords": ["pascal", "fpc", "free pascal"]
}

For testing before publishing:

code --install-extension binaries/dist/wvds-vscode-core-0.1.0.vsix

Or in VS Code:

1. Extensions → „…“ → „Install from VSIX…“
2. Select the VSIX file

Cause: vsce not installed.

Solution:

npm install -g @vscode/vsce

Cause: Publisher ID in package.json does not match registered publisher.

Solution:

1. Check the Publisher ID in package.json
2. Ensure the publisher is registered

Cause: This version was already published.

Solution:

1. Increment the version number
2. Use the increment function

Cause: Personal Access Token expired.

Solution:

1. Create a new PAT
2. Enter it on the next publish

• Build Extension - Compilation
• Core Extension - Toolchain
• VS Code Publishing Docs