Frequently Asked Questions (FAQ)

Answers to common questions about the WvdS FPC RAD Studio suite.

At least VS Code 1.85.0. We recommend the latest stable version.

Check:

code --version

Not mandatory, but recommended.

• With Lazarus: All features available, easier setup
• Without Lazarus: Only FPC, no LCL GUI projects

For desktop GUI projects with LCL, Lazarus is required.

Yes, with limitations.

code --uninstall-extension wvds.wvds-vscode-core
code --uninstall-extension wvds.wvds-vscode-build
# ... other extensions

Or: In VS Code Extensions → Right-click → „Uninstall“

Possible causes:

1. Unit paths not configured - Check the project settings
2. Incorrect case - Linux/macOS are case-sensitive
3. Unit not compiled - Ensure the unit exists

Solution: Add unit paths in the project settings.

FPC cannot find a referenced unit.

Steps to resolve:

1. Check the spelling in the uses clause
2. Check if the unit file exists
3. Add the path to the unit search paths

Native cross-compilation:

1. Install FPC cross-compiler
2. Select target in project settings

With WSL (Windows):

{
  "wvds.toolchain.wslEnabled": true,
  "wvds.toolchain.wslDistribution": "Ubuntu-22.04"
}

Possible causes:

1. Many units - Incremental build helps
2. Antivirus - Add exception for project folder
3. Network drive - Use local storage

Tips:

1. Use „Build“ instead of „Rebuild“
2. Enable smart linking
3. Reduce debug information in release

Not directly at this time. PXAML is a new format with a different concept.

Alternatives:

• Recreate in the Designer
• Convert manually
• Tool development planned

Steps to resolve:

1. Save the file (Ctrl+S)
2. Check wvds.preview.autoRefresh
3. Run WVDS: Refresh Preview
4. Check for PXAML syntax errors

Yes, but limited at design time.

• Binding syntax is supported
• Static values are displayed
• Real data binding only at runtime

1. File → Add Folder to Workspace…
2. Add project folders
3. File → Save Workspace As…

Partially. The syntax is supported, but:

• Delphi-specific units are missing
• VCL is not supported
• Project files (.dproj) are not read

Recommendation: Migrate project to FPC/Lazarus.

Options:

1. Shared folder: Units in common folder, configure paths
2. Package: Create Lazarus package
3. Copy: Copy unit (not recommended)

1. Create publisher account at VS Marketplace
2. Create Personal Access Token at Azure DevOps
3. Run WVDS: Publish Package

Common reasons:

• README missing or empty
• Version already published
• Invalid package.json
• Publisher ID mismatch

Check the Terminal output for details.

Yes, without Marketplace:

1. Create VSIX package
2. Distribute file internally (network, email, etc.)
3. Installation: code –install-extension file.vsix

Solutions:

1. Restart VS Code
2. Uninstall and reinstall extension
3. Check Developer Console (Help → Toggle Developer Tools)

Solutions:

1. Check if the extension is activated
2. Wait after startup for complete activation
3. Check dependencies (Core extension installed?)

VS Code Output:

1. View → Output
2. Dropdown: „WvdS“

Extension Host Log:

1. Help → Toggle Developer Tools
2. Console tab

Build logs:

1. Terminal panel
2. binaries/logs/ (if configured)

GitHub Issues: github.com/ArmandoFilho/WvdS.FPC/issues

Please include:

• VS Code version
• Extension version
• Operating system
• Steps to reproduce
• Error messages (log excerpts)

• Documentation: These wiki pages
• GitHub: github.com/ArmandoFilho/WvdS.FPC
• Issues: Bug Reports and Feature Requests