Forum Discussion
ClickOnce application downloads instead of directly opening the app
CodeDJ , thanks for the feedback! We would definitely need to think through some interesting security implications here (it would be analagous to setting "Always run executables" for downloads).
Vidmo , sorry I couldn't get back to you earlier; it looks like you were able to answer your question. We do not currently have plans to enable ClickOnce for ALL users, but you currently should have access to group policy to ensure that your organization has ClickOnce turned on by default if necessary. The policy is described here https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#clickonceenable
aclowe , please take a look at https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#clickonceenabled for the group policy to support exactly what you mentioned
As Eric mentioned, we will be looking into the vsto bug! Thanks everyone for your feedback!
Our customers have relied on Microsoft .NET ClickOnce support for a long time, and we are unclear how to document the path forward with Edge chromium.
- Will Edge chromium supplant existing Edge HTML installations via Windows Update?
- Will ClickOnce be disabled by default?
- Will there be a way for end users to enable ClickOnce support via settings, without having to resort to group policy or developer flags?
- Why is there now a mime-type dialog displayed asking the user to select an application for launching the ClickOnce application? Shouldn't Edge chromium be associated with .application files without an end user decision?
We obviously prefer to have ClickOnce enabled by default, but if not there should be a simple configuration option each user can toggle. We don't have any plans to retire our ClickOnce feature at this time, so continued support is critical.
- Eric_Lawrence
Microsoft
1. Yes, the new Edge will start replacing the old Edge on Windows PCs next year.
2. ClickOnce is presently disabled by default.
3. ClickOnce support can be enabled via edge://flags and Group Policy. There's no option in edge://settings.
4. A screenshot and/or OS information should be helpful here. File associations are owned by Windows, not the browser. If you save a .application file to your desktop and open it on the machine in question, what happens?
Eric_Lawrence wrote:
4. A screenshot and/or OS information should be helpful here. File associations are owned by Windows, not the browser. If you save a .application file to your desktop and open it on the machine in question, what happens?Per 4), in Version 80.0.361.40 (Official build) beta (64-bit) on Windows 10 Pro (1903) (64-bit), upon accessing a ClickOnce URL for the first time, the user is prompted to either open the file or cancel (as expected), but when the user clicks Open, a system app chooser is displayed and the user is forced to choose Edge to open the file, rather than Edge simply handing off to dfshim.dll or VSTOInstaller and letting ClickOnce do its thing. After associating .application and .vsto manifests with Edge (selecting "Always use this app" is not necessary), the user is never subsequently prompted to choose applications. The system's file association for these types is not altered, nor is it set to Edge, so this is not on the OS. On Windows, it should be Edge's responsibility to provide the manifest URLs directly to the handler for each MIME type, and an appropriate association should not need to be established by the user.
Windows 10 Default App Chooser
Thanks,
William
I can't reproduce the mime issue anymore (Version 80.0.341.0 (Official build) canary (64-bit)). It only happened once after installing the nightly, and now it's fine. I wonder if it was due to having 3 different Edge versions running on the same system (Edge, Edge Beta, Edge Canary).
It's a Windows 10 system that had no prior ClickOnce issues with Edge or IE11. When attempting to open the .application file from the file system, the mime dialog shows it is associated with the "ClickOnce Application Deployment Support Library," which appears normal.
