Edge Beta Package Request

[jcdemarque]

Hello,

we have an application that runs on Edge and is causing us problems because if the process is launched before a USB certificate key is connected, the key doesn't appear.
So we wanted to deploy Edge Beta and use it with our application.
However, the WAPT store only offers Edge, and the package disables updates. Therefore, if we manually deploy Edge Beta, it will never be updated unless we update it ourselves.

Would it be possible to add a package to the store for Edge Beta with the same configuration as regular Edge, please?

https://explore.microsoft.com/en-us/edg ... =938691289

https://c2rsetup.edog.officeapps.live.c ... brand=M103

Would this be possible?

Thank you and have a good day!

[italbot]

Hello,

I don't think we would put a beta version of software on the store, however, we can look into helping you create the package.
In your case, you want the software to update itself, if I understand correctly?

Sincerely,

Ingrid

[jcdemarque]

Ideally, yes, but the Edge package from the store disables official updates, and therefore the Beta package relies on the same keys and mechanisms to update itself, so it won't be able to update.
Unless I create a second Edge package that doesn't disable automatic updates, I'm stuck manually maintaining my Edge Beta package.

[dcardon]

Hello Jean-Charles,

I'm trying to understand the need. If I understand correctly, the Edge Beta version works properly with your signing key, while the release version doesn't? Is that right? In that case, is the need for an Edge Beta version only there while waiting for the fix to be released in Edge?

Have you tested with Firefox, Chrome, Chromium, etc.? It's not uncommon to have several browsers for the same user (we even have clients who have multiple versions of Firefox for the same user depending on the web application... ).

This is the first time we've had this request, and I don't think it's a need that's currently widespread enough to warrant putting it on the WAPT store. However, it's quite easy to duplicate and modify the tis-edge package to tis-edge-beta by modifying the four registry keys to re-enable automatic updates.

Best regards,

Denis

[jcdemarque]

Indeed, our electronic signature tool, Fast Parapheur, uses a USB signature key.
If the user has already launched Edge and then plugs in the key, the signature cannot be completed.
If Edge's cache is already full, the signature cannot be completed.

We tried launching the signature in private browsing mode, but the Fast Signature extension deactivates, and since Edge is already launched most of the time for various applications, the USB key doesn't reappear correctly.

Our idea was to create and deploy an Edge Beta package with the Fast Signature extension, so that nothing interferes with the operation when using the signature key.

If I create the package myself, I will have to update the package in my store with each update of the Edge Beta package, in addition to managing the updates of the "stable" Edge version that I retrieve from your store.

I didn't want to add a browser to the workstation, because I would inevitably receive requests for Chrome/Chromium.

If I re-enable updates in the Beta package, it might activate them on Edge, and I've already had issues with an update that broke Word/Excel files from downloads. With deployment controlled by the WAPT store, we avoid too many problems with buggy versions of Edge.

Otherwise, I'll resort to deploying Brave and its GPOs to force the deployment of the Fast Parapheur extension.

It's not really a package issue, but rather a problem with the functionality of an extension that requires a USB drive before the browser starts.

[dcardon]

Hello Jean-Charles,

if the extension and the website work with Firefox, one possibility is to create a "portable Firefox" installed in %program files% with the Fast Parapheur extension, modifying the logo and customizing the configuration to prevent it from being used for anything other than the website in question.

Regards,

Denis

[jcdemarque]

Thank you for your feedback.

I'll look into creating a package with Brave as a dependency and configuring what I need. Thanks for your suggestions, we can close this topic!