Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add article section "Writing the chrome_native_messaging_host.exe app" #2869

Merged
merged 15 commits into from
Jan 18, 2024
Merged
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ author: MSEdgeTeam
ms.author: msedgedevrel
ms.topic: conceptual
ms.prod: microsoft-edge
ms.date: 03/31/2021
ms.date: 10/13/2023
---
# Native messaging

Expand All @@ -22,6 +22,25 @@ To acquire the extension and native app host, there are two different distributi
To create your extension to send and receive messages with native app hosts, do the following steps.


<!-- ====================================================================== -->
## Writing the chrome_native_messaging_host.exe app

Writing the chrome_native_messaging_host.exe app - this section provides code examples in multiple programming languages.

How you actually write the chrome_native_messaging_host.exe application.

stdin and stdout are used to communicate with the host.

How the information sent from the extension is encoded.

Perhaps:
The first four bytes is a number that specifies packet length, and the rest is the packet data encoded as JSON.

How to encode the information that is sent back to the extension: tbd

How the chrome_native_messaging_host.exe application knows when to exit: tbd


<!-- ====================================================================== -->
## Step 1 - Add permissions to the extension manifest

mikehoffms marked this conversation as resolved.
Show resolved Hide resolved
Expand Down