Closed GoogleCodeExporter closed 8 years ago
You can setup Group Policy to push out the registry value.
See the uploaded image for the setup I used. Just add that to the User
Config/Preferences/Windows Settings/Registry section of Group Policy.
This will only work on the 32 bit version of Chrome and only for another few
months as Google is phasing out NPAPI.
In case the image doesn't show up here are the settings:
Hive HKEY_CURRENT_USER
Key path Software\MozillaPlugins\@digitalsorcery.net/ClickOnceForChrome;1.2
Value name Path
Value type REG_EXPAND_SZ
Value data \\<YOUR SERVER
INFO>\Extensions\clickonceforchrome-a4ee7cfb6925\Extension\plugin\npclickonce.dl
l
Original comment by infinite...@gmail.com
on 26 Aug 2014 at 8:31
Attachments:
Ok thank you for the tip.
One more thing, do you think that google phasing out NPAPI means that they will
not host NPAPI plugins on the store anymore or that future Chrome version won't
run NPAPI plugin at all ?
Thank you !
Original comment by gilles.l...@gmail.com
on 1 Sep 2014 at 10:00
Ok, find out, futur chrome version won't support / run NPAPI based plugins.
Original comment by gilles.l...@gmail.com
on 1 Sep 2014 at 11:30
[deleted comment]
[deleted comment]
[deleted comment]
Hi! Current dev here.
There is a new version which no longer needs NPAPI.
https://chrome.google.com/webstore/detail/eeifaoomkminpbeebjdmdojbhmagnncl
As for mass deployment:
1) You will need the helper application from www.clickoncechrome.com
2) Extract the zip file.
3) Then add a registry entry for
HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.google.chrome.
clickonce
The value should be the path to the .json config file inside the helper
applications bin directory.
e.g.: C:\ClickOnceLauncher\bin\com.google.chrome.clickonce-win.json
Or simply run the Setup file that comes with archive.
Original comment by bionicma...@gmail.com
on 25 Sep 2014 at 7:38
I'm a bit late but a big thank you for the new version. You can't imagine how
usefull is this and how big comps use it... ;)
Original comment by gilles.l...@gmail.com
on 8 Dec 2014 at 9:12
Original issue reported on code.google.com by
gilles.l...@gmail.com
on 16 Jul 2014 at 9:29