IDE Integrations

VS Code

IDE extension.

Overview

Use Visual Studio Code to review application changes and the evidence produced by your approved validation workflow.

Prerequisites

  • An authorized practice repository and a known source revision.
  • The project’s approved tooling instructions and access to the relevant service.

Step-by-step procedure

Prepare the workspace

Choose the repository and local or remote workspace. Use the tools already approved for that project. Confirm the publisher and supported version before installing any Zof-specific extension; this guide does not establish that a marketplace extension exists.

Review execution and data boundaries

Review workspace trust, tasks, extension permissions, and access to local credentials. A repository can define commands that execute when a task or debug configuration is started.

Verify the workflow

Check out a known revision and follow the project’s documented validation process. Compare the evidence with the source change and ensure generated files are reviewed before committing.

Best practices

  • Keep the source revision, configuration, and evidence together when reporting a result.
  • Review generated changes before merging them into a shared branch.
  • Remove practice credentials and temporary artifacts when the exercise is complete.

Common issues

Environment mismatch
Check the active workspace, interpreter or runtime, task environment, and whether execution occurs locally or on a remote host. Do not assume an editor setting is applied to a separate CI runner.

Was this page helpful?