Apr 08 2019 10:01 AM
Apr 08 2019 10:01 AM
When opening a ClickOnce app, the *.application file gets saved to my Downloads folder instead of directly opening it. Additionally, since the file is downloaded, then opened from Downloads, it loses the cookie information required for our app to function correctly.
Apr 08 2019 10:12 AM
I'm experiencing this as well. This is known behavior for how Chrome handles ClickOnce applications, but we use Edge today for launching ClickOnce applications.
Apr 08 2019 10:28 AM
@CodeDJ I have this same issue. I get around it by calling iexplore.exe in front of the app to launch it from IE. This is a workaround, I would like Microsoft to fix this so it is handled correctly.
Here is my example that I use in the shortcut:
"C:\Program Files\Internet Explorer\iexplore.exe" http://website.com/example.application
Apr 08 2019 10:36 AM
@Jesse Cook Thanks for the tip. Clicking on the downloaded abc.application opens the clickonce app for me using Edge Insider but it doesn't include any cookies from my website - which is a requirement for my apps. Thanks!
Apr 08 2019 02:24 PM
Yep same here, this was one of the first things I wanted to check as we really need this to be working out of the box for the new Edge.
Apr 10 2019 12:05 PM - edited Apr 10 2019 12:06 PM
@CodeDJ There is a Chrome extension called "ClickOnce for Google Chrome". This can be installed in Edge, if you allow extensions from other stores and then acquire the extension from the Chrome Web Store. Although, this is not a built-in function, the extension does allow ClickOnce apps to execute normally, instead of being downloaded.
I do hope that this ClickOnce function will be addressed in Edge, so that we don't have to use an extension or another work-around.
Apr 10 2019 05:52 PM
@CodeDJ We really appreciate the feedback! ClickOnce support was on our mind as we were thinking through the Downloads workflow in Edge. It is feedback like yours, and others responding to this post, that help us in prioritizing ClickOnce support relative to other areas we are investing in. ClickOnce is a feature that we are working towards implementing, so stay tuned!
May 30 2019 07:02 PM
Hi @Vidmo, thanks for checking in! We have engineers actively working on getting ClickOnce support and this is high on my priorities. While I can't reveal the timeline for this, I will try to update this post when I have more information to share. Feel free to ping this thread again if you don't hear back from me!
Jun 17 2019 05:39 AM
Jun 20 2019 07:08 PM
Jun 21 2019 10:18 AM
@aclowe Thanks for the feedback, it definitely helps that we can show customer need when prioritizing our features. Engineering work is still being put into this feature, so it is definitely still a priority! Will keep people updated via this thread!
Sep 23 2019 11:05 AM - edited Sep 23 2019 11:07 AM
@CodeDJ Just updating this thread to say that ClickOnce support is now in Canary (79.0.283.0). Users may opt into using ClickOnce by heading to the about:flags page and looking for "#edge-click-once".
More information on this is available here:
Thanks everyone for your patience!
Sep 24 2019 10:23 AM
@i-am-kent awesome! I have verified it works as expected, except for what's documented in the url you provided. For our internal website, I keep getting the Open/Cancel popup and have to click it each time.
Sep 25 2019 06:35 AM - edited Sep 25 2019 08:19 AM
@i-am-kentI read the documentation page you listed and I'm confused. Why would ClickOnce NOT be turned on by default?
We're expecting a solution that behaves as IE and Edge do today. They both have ClickOnce on by default, why shouldn't Edge DEV as well? Also, will there be a GPO method to turning this on? If not, then how can you claim it's for Enterprises to use?
Sep 25 2019 07:30 AM
@Vidmo this is how they release new features, first in canary, a lot of times behind a flag, when stable it becomes the default.
Sep 25 2019 08:17 AM - edited Sep 25 2019 08:19 AM
@CodeDJPlease re-read the documentation page. https://docs.microsoft.com/en-us/DeployEdge/edge-learn-more-co-di?branch=pr-en-us-105
That page states specifically "Because ClickOnce is an enterprise-focused feature that’s used by a specific group of power users and not intended for general use, ClickOnce is disabled by default."
Sep 25 2019 08:24 AM
@i-am-kent To somewhat answer my own question about GPO support it looks like the manual enable option does state that "This feature flag will be overridden if your organization configures the "Allow users to open files using the ClickOnce protocol" policy."
So maybe we will have some control over this.
Sep 25 2019 09:50 AM
@i-am-kentJust tested with a ClickOnce .application URL and it worked fine. But what about .vsto? Its not being treated as a ClickOnce URL install.
Sep 25 2019 11:05 AM