Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>VBA-JNew to Visual Studio Code? Get it now.
VBA-J

VBA-J

Jyaaru

|
5 installs
| (0) | Free
Sync Excel VBA modules with a VS Code workspace through a bundled helper.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

VBA-jyaaru VS Code Extension

VBA Jyaaru is a Visual Studio Code extension for Excel VBA development.

It helps you export VBA modules from an Excel workbook into a VS Code workspace, edit the exported source files, and automatically synchronize changes back to Excel.

VBA development workflow: export Excel VBA modules, bind them to a workspace, and reflect .bas file changes back into Excel automatically.

Features Export VBA modules from an Excel workbook to a local workspace. Bind an Excel workbook to a VS Code workspace. Edit exported VBA source files such as .bas, .cls, and .frm. Watch the workspace for file changes. Automatically import updated VBA files back into the bound Excel workbook. Manage export/import sessions from the VS Code sidebar. Open the export directory directly from VS Code. Show the current synchronization status. Supports English, Japanese, and Simplified Chinese UI text. Typical Workflow Open a workspace in VS Code. Select an Excel workbook. Select an export directory. Export VBA modules from the workbook. Edit the exported VBA files in VS Code. Start watching the workspace. When a VBA source file is changed, the extension imports the updated content back into Excel.

This allows you to use VS Code as the main editor for Excel VBA source code while keeping the Excel workbook synchronized.

Commands

The extension contributes the following commands:

Open Panel Open the VBA Jyaaru control panel. Add Session Create a new workbook/workspace synchronization session. Select Session Select an existing synchronization session. Select Workbook Choose the Excel workbook to bind with the current workspace. Select Export Directory Choose the directory where VBA modules will be exported. Export Export VBA modules from the selected Excel workbook to the workspace. Import Import VBA source files from the workspace back into the selected Excel workbook. Start Watch Start watching the exported VBA files. When files change, the extension synchronizes them back to Excel. Stop Watch Stop file watching. Show Status Show the current session and synchronization status. Open Export Directory Open the configured export directory. Requirements Windows x64 Visual Studio Code 1.90.0 or later Microsoft Excel .NET 10 x64 Runtime for the framework-dependent VSIX. Not required for the self-contained VSIX.

The extension uses a .NET helper executable to communicate with Excel and handle VBA import/export operations.

Packaging Notes

During development, the extension starts the .NET helper from:

dotnet-helper/VbaJyaaruHelper/bin/Debug/net10.0-windows/win-x64/vba-jyaaru-helper.exe

For default release builds, the .NET helper is published as a framework-dependent single-file executable:

bin/vba-jyaaru-helper.exe

The default helper executable does not bundle the .NET runtime. Therefore, the target machine must have the .NET 10 x64 Runtime installed.

To build a Windows x64 VSIX that bundles the .NET runtime, run:

package_vsix_self_contained.bat

This creates:

vba-j-self-contained-win32-x64.vsix

Users who install this self-contained VSIX do not need to install the .NET runtime separately.

The extension only uses the helper executable. If the helper is missing, startup fails with a clear error message.

Extension Settings

This extension contributes the following settings:

vbaJyaaru.helperPath

Custom path to the VBA Jyaaru helper executable.

If this value is empty, the extension uses the bundled helper executable from the extension bin directory.

vbaJyaaru.language

Controls the extension UI language.

Available values:

auto - Use the VS Code display language. zh-cn - Simplified Chinese. ja - Japanese. en - English. Notes

VBA Jyaaru is designed for Excel VBA projects where source files should be managed outside the workbook.

It is useful when you want to:

edit VBA code in VS Code; track VBA source files with Git; keep workbook modules synchronized with local files; avoid manually importing and exporting .bas, .cls, and .frm files.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft