ContextConsole Shell Extension — Install, Configure, and Master

ContextConsole Shell Extension — Install, Configure, and Master

What it is

ContextConsole Shell Extension adds context-menu (right-click) options in Windows Explorer to open a terminal at a folder, run commands, or launch configured shells (PowerShell, CMD, WSL, etc.) directly from file and folder contexts.

Install

  1. Download the installer or ZIP from the official project page (choose 32-bit vs 64-bit to match your Windows).
  2. If ZIP, extract to a folder.
  3. Run the installer as Administrator, or register the DLL manually:
    • Installer: double-click and follow prompts; allow UAC elevation.
    • Manual (advanced): open an elevated Command Prompt and register the extension DLL with:

      Code

      regsvr32 “C:\path\to\ContextConsole.dll”
  4. Reboot or restart Windows Explorer to apply.

Configure

  1. Open the extension’s settings UI (from Start menu or its context-menu entry “Settings” if provided).
  2. Set default shell(s): point to executable paths for PowerShell, cmd.exe, Windows Terminal, or WSL (wsl.exe).
  3. Configure menu entries: enable/disable items shown for folders, background, files, or drives.
  4. Add custom commands:
    • Specify label, command line (use placeholders like %1 for selected path), starting directory, and whether to run elevated.
    • Example command: label “Open with Node” — command cmd.exe /k “cd %1 && node”
  5. Set keyboard modifiers (e.g., show advanced options only when Shift is held).
  6. Choose icons, sorting, and whether to show for directories only or for files too.

Usage tips & workflows

  • Open terminal at current folder: Right-click folder background → select desired shell.
  • Open terminal at selected file’s folder: Right-click file → choose “Open terminal here”.
  • Run quick commands: Configure custom command entries like “Run tests” that execute a build/test script in the folder.
  • Use placeholders: %1 = selected path, %L = long path, %V = verbatim path; check extension docs for exact tokens.
  • Combine with Windows Terminal by pointing commands to wt.exe for tabs/profiles.

Troubleshooting

  • Menu doesn’t appear: ensure DLL registered, extension enabled in Settings, and Explorer restarted.
  • Wrong architecture: use 64-bit build for 64-bit Windows Explorer.
  • Commands not running elevated: mark command as “Run as administrator” or configure a helper that triggers elevation.
  • Path placeholders incorrect: test commands using a simple echo command to verify substitution: cmd.exe /k echo %1.

Security

  • Only add trusted commands; commands run with your user privileges and can be elevated if configured.
  • Review custom command strings to avoid injection through untrusted filenames.

Short checklist

  • Download correct build → Install/register → Restart Explorer.
  • Set default shell and add useful custom commands with %1 placeholder.
  • Verify menu appears and test each command.
  • If issues, re-register DLL or use the installer as Admin.

If you want, I can generate a ready-to-run example configuration file or specific custom-command templates (PowerShell, WSL, Windows Terminal).

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *