VS Code open project folder with context menu

VS Code open project folder with right click from explorer context menu

If you develop with VS Code, a project folder is also used in here. VS Code stores the workspace settings in the settings.json file. The setting for the debugger in launch.json under the .vscode folder of the respective project folder.

Open VS Code project folder via explorer context menu

When VS Code is installed, the context menu is automatically expanded, allowing a file to be opened from the Explorer context menu in VS Code. Unfortunately, opening a directory from the context menu was lost. This post shows how to expand the context menu to open folders for VS Code.

VS Code reads the project settings by entering code .in the respective folder. The following registry key can be added. This makes it possible to open the selected project folder in VS Code via the explorer context menu.

Add VS Code context menu to registry

REG ADD HKCR\Directory\shell\Code /ve /t REG_SZ /d "Open" /f
REG ADD HKCR\Directory\shell\Code\command /ve /t REG_SZ /d "%localappdata%\Programs\Microsoft VS Code\Code.exe \"%V\"" /f
REG ADD HKCR\Directory\shell\Code /v Icon /t REG_SZ /d "%localappdata%\Programs\Microsoft VS Code\Code.exe" /f

Copy Paste the lines in a command prompt opened as administrator.

  It may be that your system has’t VS Code installed under %localappdata%\Programs. Make sure you know which path code.exe is installed in and, if necessary, modify the path in the last two lines.

Initially, the previous VS Code versions were not installed from the Microsoft store, but were deployed in Program Files, then add this keys.

REG ADD HKCR\Directory\shell\Code /ve /t REG_SZ /d "Open" /f
REG ADD HKCR\Directory\shell\Code\command /ve /t REG_SZ /d "C:\Program Files\Microsoft VS Code\Code.exe \"%V\"" /f
REG ADD HKCR\Directory\shell\Code /v Icon /t REG_SZ /d "C:\Program Files\Microsoft VS Code\Code.exe" /f

Copy Paste the lines in a command prompt opened as administrator.

The new “Code” context menu is now registered.

Right-click above the selected folder, in the context menu click “Open” at the blue code symbol.

VS Code open project folder with context menu

Note. In Windows 11, under “Show more options” you can find the context menu with the VS Code you just added.

Remarks

The Lightweight Editor VS Code is a cross-platform editor for developers that differs from integrated development environments (IDE). Like Sublime, Atome or Eclipse, Visual Studio Code still supports debugging and autocompletion with IntelliSense. However, it does not include integrated compilers and components such as version management, project management, or the ability to easily create graphical user interfaces (GUI).

However, Visual Studio Code makes it possible to adapt the development environment (IDE) to the required development workflow. With a variety of extensions, VS Code can be expanded in many ways, so additional features can be integrated from the marketplace, such as extensions for version control and debugger tools. The interpreters and compilers of the languages must be provided according to the platform and version.

Mail Server FQDN 450 Helo command rejected: Host not found

Mail Server FQDN – NOQUEUE: reject: RCPT from mail.example.org: 450 4.7.1: Helo command rejected: Host not found.

Mail server MTA (Mail Transport Agent) check incoming SMTP requests for the A Resource Record or CNAME which is registered with the authorized DNS server, the condition being that the mail server FQDN sent with EHLO/HELO is based on the A (AAA) or CNAME Resource Record must show.

quote  Incoming messages are rejected as bounces that send a different FQDN to EHLO.

NOQUEUE: reject: RCPT from mail.example.org[203.0.113.32]: 450 4.7.1 <mail.server.net>: Helo command rejected: Host not found.

Exchange server FQDN incorrectly

Exchange mail servers that are configured for direct delivery must specify the FQDN valid in the DNS (mail.server.net) in mail flow (message flow) in send connectors under scoping (area definition) FQDN in HELO/EHLO.

Mail server FQDN Helo command rejected Host not found
Abbildung: Exchange send connectors scoping FQDN

ECP: mail flow -> send connectors -> scoping -> FQDN

Checking the configuration mxtoolbox.

Remarks

This article describes the bounce error, which causes EHLO to send a different FQDN when incoming messages are discarded. The result is “Helo command rejected Host not found”. Mail servers that are configured for direct delivery must specify the valid FQDN (mail.server.net) in the DNS for mail flow for send connectors under scoping for HELO/EHLO.

The value specified here is sent to the recipient’s mail server during the SMTP connection using the HELO/EHLO command. At this point, the remote server will then perform a reverse DNS record lookup (PTR) on the IP address you are connecting from and attempt to match the two values. If they don’t match, many mail servers give the message SPAM points or reject the message entirely. To prevent this, one must ensure that the DNS is set up correctly for the IP address(es) that will be selected for outbound delivery.

Example of the mail server that was set up with the IP address 203.0.113.32.

IP – Host Name
203.0.113.32 mail.example.org

The following must be the case.

mail.example.org -> must be resolved -> 203.0.113.32
203.0.113.32 -> must be resolved -> mail.example.org

  The HELO/EHLO name should be the fully qualified domain name (FQDN) of the system.

quote  if email is sent from the IP address 203.0.113.32, and mail.example.org resolves to 203.0.113.32 (and the DNS PTR for 203.0.113.32 is set to mail.example.org), mail.example.org can be used as value for HELO (EHLO).