Talk:ClickOnce
![]() | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||
|
This entire article
[edit]This entire article has been copy/pasted from: http://msdn.microsoft.com/smartclient/understanding/windowsforms/2.0/features/clickonce.aspx
Agreed. This article does seem a bit like a marketing ploy. I would recommend a rewrite for better balance. —Preceding unsigned comment added by 161.6.65.168 (talk) 18:31, 22 June 2009 (UTC)
I can't even particularly tell if there's a difference between this and Side-by-side assembly. Is a merger in order? Reinderientalk/contribs 23:46, 22 June 2009 (UTC)
Started a short article replacement
[edit]Someone should point out that Clickonce is now natively supported by Firefox from Visual Studio 2008 beta 2 and up ... Fegelein 02:53, July 31, 2005 (UTC)
Started the article with a basic summary of what ClickOnce is. Feel free to expand, but not using any of the text at the MSDN link.
- Temp page has replaced the main article. RedWolf 02:53, July 31, 2005 (UTC
Sample?
[edit]Is there a sample ClickOnce application ready for download on the Web which I can try to test the technology? There are plenty for Java Web Start. - Sikon 05:35, 15 August 2006 (UTC)
In VS2005, press "Publish" on a project in the Solution Explorer tree to publish the project.
Needs Updating
[edit]"ClickOnce applications must be signed with an Authenticode Digital Certificate." - this is not true
Reply: Yes This is true, please see article from MSDN MSDN: "All ClickOnce deployments must be signed with a digital certificate. "
- If it is true, then how come the example screenshot says it was NOT signed ("unknown publisher")? 120.151.160.158 (talk) 15:03, 15 February 2012 (UTC)
- Being signed by an unknown publisher does not mean it is not signed. It just means it is signed by an unknown publisher. You can't have an unknown publisher if you don't sign it. -Rushyo Talk 11:50, 22 January 2013 (UTC)
Firefox Integration
[edit]I have made the following update, as I have learned that the integration with Firefox only occurs with SP1 (Service Pack 1).
Changed "ClickOnce prior to .NET 3.1" to "ClickOnce prior to .NET 3.1 SP1" as Firefox integrations only occurs officially with SP1
Somebody may correct me if I'm wrong, but I have learned this from personal experience as well as research on the MSDN website. —Preceding unsigned comment added by 137.48.219.72 (talk) 20:03, 26 January 2009 (UTC)
As per: http://blogs.msdn.com/brada/archive/2009/02/27/uninstalling-the-clickonce-support-for-firefox.aspx
The update at: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cecc62dc-96a7-4657-af91-6383ba034eab
Means that this can be uninstalled easily now, so the text referring to it only being uninstallable by a registry edit is no longer accurate. FleckerMan (talk) 17:26, 24 May 2009 (UTC)
No Administrator privileges are required
[edit]In the description there is the following sentence: ClickOnce-deployed applications are considered 'low impact', in that they are installed per-user, not per-machine. No administrator privileges are required to install one of these applications. Each ClickOnce application is isolated from the other. Well, this is not true anymore as soon as a user must also - as a prerequisite of his application - install WindowsInstaller or the .NET framework. Shouldn't at least a hint on this be added, I think it's misleading? --193.134.202.252 (talk) 15:26, 14 May 2010 (UTC) e_l_
Needs a Critism section.
[edit]When I google:
define: microsoft .net framework assistant Add-on ,
I land here in Wikipedia. Check it out. Among the first hits:
From the Firefox browser addon site: "Rated 2 out of 5 stars Average." and: "So the NFA is the most used add-on for Firefox- yet it is rated 2 stars and everyone here is trying to get rid of it. The only way it gets onto Firefox in the first place is by sneaking it in as a security update." Also: washingtonpost.com > Technology > Security Fix May 29, 2009: "Apparently, the .NET update automatically installs its own Firefox add-on that is difficult -- if not dangerous -- to remove, once installed." and "this is a great example of how not to convince people to trust your security updates." ... so on and so forth. Please do check it out... Needs a critism section.
--69.110.89.115 (talk) 18:13, 13 September 2011 (UTC)Doug Bashford
Uptake?
[edit]How much is ClickOnce used in practice? Am I right in the assumption that - at least on the public internet - it's not exactly a widely used technology? -- 77.189.45.149 (talk) 16:25, 10 November 2011 (UTC)
- I just ran into it for the 1st time and wound up here. The lastest HP_Integrated_Lights-Out make use of it. Can't say the article was very useful. --Alapolloni (talk) 09:39, 17 October 2013 (UTC)
FxClickOnce
[edit]FxClickOnce allows ClickOnce support in Firefox (on Windows) without installing Microsoft's plugin [1]. Obviously I'm not going to add it to the article since I wrote it (WP:NPOV), but the article mentions its predecessor (FFClickOnce) and it would seem to fit with the existing theme of the article if somebody feels it merits inclusion. -Rushyo Talk 11:54, 22 January 2013 (UTC)
Security impact
[edit]Seems like an inevitable question with any 'one click automation' gadget from Microsoft, but how exploitable is this? For a start it would seem to allow non-admin users to install software which they shouldn't be installing, furthermore it seems quite likely they could be duped into doing so by way of social engineering tricks. Since XML files are used for other benign purposes on websites it also seems an insanely bad idea to have a situation where an XML file can unexpectedly download and install executables. The only actual usage I've encountered so far is on the Navman website for their PC software. --Anteaus (talk) 22:14, 11 March 2013 (UTC)