-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClickOnce fails in Chrome and Firefox #345
Comments
@yodurr thanks for raising this. This has been a known issue for a while, and it comes down to the fact that Chrome removed support for NPAPI: https://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html It is my understanding that ClickOnce relies on this in order to function, and as a result, fails. As a result, I don't think that there is much that Boxstarter itself, can do to work around this. @Redsandro has created a Google Chrome extension (https://chrome.google.com/webstore/detail/windows-remix-clickonce-h/dgpgholdldjjbcmpeckiephjigdpikan) which adds support for ClickOnce back into those browsers, however, this would need to be installed, prior to trying to access a Boxstarter URL. @yodurr did you have any suggestions on how to workaround this in another way? |
@yodurr Did you manage to get this working in Chrome? |
no, it still doesn't work. Am using the scripts on aka.ms/devsetup |
As far as I understand it this is a browser issue and outside of Boxstarter. Not sure what we can add to that. I know there are plugins for Chrome and Firefox - I have no experience of them so cannot make any recommendations. I was hoping you were going to come back with a 'yeah, and here is a fantastic plugin that works really well' ... :( |
At some point, IE will be dead and the Edge that runs with NPAPI will also be dead, replaced by the Chromium Edge. https://www.windowscentral.com/microsoft-building-chromium-powered-web-browser-windows-10 |
Running the clickonce installer fails to start in Chrome. It's a known issue and the workaround is to use Edge. I didn't see an issue for it so adding the issue here.
The text was updated successfully, but these errors were encountered: