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

Native messaging and MSIX packaging: No docs on how an extension might be packaged with MSIX #150

Open
minfrin opened this issue May 13, 2024 · 1 comment

Comments

@minfrin
Copy link

minfrin commented May 13, 2024

The docs at https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/native-messaging?tabs=v3%2Cwindows describe how a json manifest and a native application can be made known to Microsoft Edge.

What isn't documented is how a native application can make Edge aware of itself when the native application is packaged as an MSIX file.

Questions the docs need to answer:

  • What must be done within the MSIX packaging to place the JSON and native application somewhere where Edge can see both files?
  • What must be done within the MSIX packaging to place the registry entry where Edge can see it?
@sivMSFT sivMSFT assigned sivMSFT and unassigned sivMSFT May 16, 2024
@sandeepchads
Copy link

@minfrin thanks for the feedback. Would love to understand your scenario in a little more detail. Can you please explain the problem that you are trying to solve with the MSIX package and its need to talk to Edge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants