What do we call ClickOnce?
Right now, ClickOnce is a code name. We need a real name. What should it be?
Comments
- Anonymous
July 10, 2004
As long as it's less confusing as '.NET' you'll be on to a winner...Something which reenforces the security aspects of this method would certainly be useful... - Anonymous
July 10, 2004
Having Java WebStart already taken, let's try:
NetStart - WebStart
NetClick - WebClick
NetLoad - WebLoad
NetRun - WebRun
NetApp - WebApp
NetLink - WebLink
NetLaunch - WebLaunch
NetGo - WebGo
donations welcome ;-) - Anonymous
July 10, 2004
I think "ClickOnce" captures the essence of the feature pretty well - a simple, secure app deployment. Why change it? I've seen to many Microsoft feature names like "Microsoft Windows Application Deployment Framework (MSWADF)" in my day.
I know a name like "ClickOnce" sounds more like something from Apple's branding conventions - but I think that's one thing Apple gets right. Their product/feature names are clear, exciting, and easy to remember. I'm tempted to say the same thing about Avalon, Indigo, and WinFS. - Anonymous
July 10, 2004
xcopy.net
or smart.net (it is going to be used mostly for smart clients)
smartDeploy
smartInstall
be carefull
http://www.smartash.com/
is already registered ! - Anonymous
July 10, 2004
Click To Run
Click and Run
Click and Go
Better Setup
Click and Ready - Anonymous
July 10, 2004
My vote is to keep it ClickOnce - Anonymous
July 10, 2004
I think it should called One Step Install - Anonymous
July 10, 2004
I think it should called One Step Install - Anonymous
July 10, 2004
How about tarconfiguremakemakeinstall.net? - Anonymous
July 10, 2004
So far, I'm liking "tarconfiguremakeinstall .NET" :-) - Anonymous
July 10, 2004
ClickTwice
After all... you'll need to click on a link of some kind of installing from the web, then after that some sort of “What do you want to do with this file?” prompt... Open. - Anonymous
July 10, 2004
I believe that there is enough thoughts behind ClickOnce. So do not change it. But if there is really need to change that then...
Something I feel might be good alternative is:
Start.NET
Launch.NET
Smartstart (YES)
Nonstop
SmartClick (YES)
ClickSet (YES)
ClickFit (YES)
Clicklet (WHY NOT)
EveryClick.NET
Every.NET
Oneclick (YES)
(ok. credits belongs to me LOL) - Anonymous
July 10, 2004
Little more...
InStart
Instant.NET
OnStart
OneStart (nice?) - Anonymous
July 10, 2004
ClickOnce is just fine as it is...
But if you simply MUST change it, the only notion that "ClickOnce" doesn't connote is that of "deployment". Hence, how about:
EasyDeploy
EasyInstall
SimpleDeploy
SimpleInstall - Anonymous
July 10, 2004
ClickOnce
Click.Once
Click.Deploy <-- It's an "Oh, I get it!" name - Anonymous
July 10, 2004
"Secure" is a buzzword at the moment. Maybe it should be in the name.
I'm against "deploy" because I don't think it will be meaningful to end-users. "Install" is definitely something my parents (one a techie; the other not) would both understand.
I'll also vote against any meaningless, unpronouncable string of letters like "NGSCB". - Anonymous
July 10, 2004
ClickOnce always undersold what you could do with the ClickOnce technologies. It is clearly capable and intended for more than just web deployment.
The new name should describe it as an install or application management scheme rather than include the verb click.
how about 'Managed Install Framework' or Manifested Install. - Anonymous
July 10, 2004
Either "ClickOnce" or "The Deploymentinator" - Anonymous
July 10, 2004
Since ClickOnce is wondows-.NET-only, requires server manifest files, I believe the only way not to sell a technology on false claims is to name it with a Win prefix or suffix. So far, WinInstallerLight matches everything. - Anonymous
July 10, 2004
I think ClickOnce is fine. It's been used as codename so long, trying to find a good new name will be hard. Also ClickOnce is fast to pronounce. - Anonymous
July 10, 2004
Among all the names suggested here so far, I think ClickOnce is still by far the best. - Anonymous
July 11, 2004
I love these ideas (both serious ones and humorous ones)!! Thanks for taking the time to do this.
What I'm getting off this thread is what I thought: ClickOnce is a good name (and kudos to Brendon who thought up "ClickTwice" -- where were you to ground my enthusiasm when I was naming "no touch deployment"? :-)).
I'll go back and push to keep the name the same.
Thanks!!
John - Anonymous
July 11, 2004
I agree that ClickOnce doesn't really tell you what it does and is really ClickTwice. Also it could be mistankenly interpreted as the opposite of double-click.
In additon please note that there is already a technology called "One-Click Install" which was created (and probably registered as trademark) by InstallShield a couple of years ago.
Therefore I vote for a new name, although I don't have better suggestions than those already listed. - Anonymous
July 12, 2004
.Deploy
Load'n'Go
SecureLaunch
SandBoxStart - Anonymous
July 12, 2004
Another vote to keep the name the same! - Anonymous
July 12, 2004
I think it really depends on the audience you're going for. If you're thinking primarilly about the VB crowd, then maybe "Clicking4Fun", to piggy-back off an existing brand (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx)
If you're really going after the C# crowd, then you need something far more serious sounding, like "Enterprise Installation Framework".
If the C++ crowd is really the target, then I'm thinking "It Just Installs (IJI)".
If you want to use it to evangelize .NET to the Java community. In that case how about "Click it, you just might like it", or maybe "Just click it!" If you really want Java developers to use it, have the links show up as "101 Reasons Why Java is Better Than .NET", just make sure you've tested for scalability. - Anonymous
July 12, 2004
Doesn't Amazon.com have bagsies on "ClickOnce" or "One Click" or something...? - Anonymous
July 15, 2004
Howabout..
JumpStart
HeadStart
GoDeploy
SwitchOn
?? - Anonymous
July 16, 2004
It should be a non-word like "Xlamf" to slow the rate at which the entire language is disappearing into corporate lawyer land.
If that is too optimistic, then at least please run it together with an existing unique identifier "Instant.NET" (as suggested above) or "MSClickOnce"