04-12-2019 12:04 AM
04-12-2019 12:04 AM
I see some others asking about deploying extensions to the store, but I seem to be stuck at finding the new documentation on how to make an extension.
I see the new Devtools Guide (chromium)
However the Extensions development documents seem to still refer to current version of Edge extensions.
04-14-2019 11:49 PM
05-20-2019 03:02 PM
+1 on "how do I publish an extension to the (insider) store", especially because I'd like to see early testing of more diverse extensions than the 118 currently listed at https://microsoftedge.microsoft.com/insider-addons/category/EdgeExtensions. None of those are a chrome_url_overrides extension as far as I can tell, like the new-tab extension I maintain.
08-11-2019 10:59 PM
@ArunKBuduri When I imported our Chrome extension it was able to use the native messaging based on the id that was assigned by Google store.
However, still, no clarity on the access control for the native messaging once the extension is published from the MS store. Assuming so far that there will be changes to the store ID.
08-11-2019 11:08 PM
@GDomjan That's great to know you have it working. When Edge automatically imported, it didn't seem to import the native host. My chrome native host json is under "/library/Google/Chrome/NativeMessagingHosts". Do you know where Edge Dev gets its json from? Did Edge make a copy of all the native host json files into its own folder anywhere?
I couldn't find any though and I don't see the native host started inside Edge.
@ArunKBuduri I'm not sure I understood your query correctly.
I used existing published extension from the Chrome store, and did not try to import from local in developer mode.
It seemed to make use of the same Chrome registry to identify the native host.
Next time I check it out I'll see if there is some migration/duplication of the native host from Chrome into the Edge space.
@GDomjan The best way to confirm this is to look at Edge processes list and check if you see native host listed among them (since native host runs inside the context of the Edge or Chrome process). This will confirm if the extension you imported from the Chrome store uses a native host (or not).