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.