ClickOnce: is one or 2 clicks possible?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This has come a LONG way since "No Touch"! Appreciations. However, is it
actually possible to achieve one click?

Reboot: After .NET FW 2.0 installed, a reboot was required on XP Pro test
box. After the reboot, the install did not continue; required to re-open
publish.htm, and click again. Install continued correctly, but the
bootstrapper for FW 1.1 didn't require a reboot on this same text box, for
the 1.1 version of the app, before the upgrade. Can the reboot be avoided?

EULA: can it be suppressed for intranet users? -- that is, corporate admins
Accept Once on their behalf?

Unknown Publisher: since it is strong named, has full trust and used only
internally, can this be suppressed without buying a 3rd-party certificate?

Thank you.
 
Hi mpbio,

Thanks for your post!

Reboot: this is the requirement of .Net Framework2.0 installation, which is
not the requirement of ClickOnce. So there is nothing we can do in
ClickOnce side.

EULA: I do not understand this question completely. Can you give a more
detailed clarify?

Unknown Publisher: do you mean that you want to configure the ClickOnce
publisher as the trusted? Please refer to the link below:
"Configuring ClickOnce Trusted Publishers"
http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnwin
forms/html/clickoncetrustpub.asp

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
EULA: I do not understand this question completely. Can you give a more
detailed clarify?
Click to expand...

I read that the bootstrapper pops up one combined Eula for all prerequisites
it installs, rather than one Eula for each, which is great. But how can
ClickOnce deployment suppress even the one Eula? (Acceptance is corporate
decision, as the company is responsible for licenses. For the user to click
the Eula here is meaningless and adds to the number of clicks we're trying to
avoid with ClickOnce.)
Reboot: this is the requirement of .Net Framework2.0 installation, which is
not the requirement of ClickOnce. So there is nothing we can do in
ClickOnce side.
Click to expand...

It's only once every Framework version; we can live with that.
"Configuring ClickOnce Trusted Publishers"
http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnwin
forms/html/clickoncetrustpub.asp
Click to expand...

Thanks! This looks good.
 
Hi mpbio,

Thanks for your feedback.

I am not familiar with Eula function in ClickOnce. Is not it an optional
feature of ClickOnce? If it still always pops up for you, can you show me
some steps to reproduce the Eula function? Once I can reproduce the Eula
behavior, I will help you to get rid of it. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Jeffrey,

I see what you mean. It's optional for the project part of the install but,
for any prerequisites, the default is to display a EULA . So, if the intranet
user needs to install .NET FW 2.0 during the bootstrap portion of the
ClickOnce install, by default they have to accept the EULA for .NET 2.0 to
complete the install.

No doubt, you're familiar with managers who positively don't want to know
about .NET 2.0. They want IT to accept responsibility for the install. So,
I'm hoping ClickOnce can be configured for AcceptOnce - at policy level,
rather than during each individual install.

Thanks, Jeffrey! (And thanks for the link to Configuring ClickOnce Trusted
Publishers. That is very useful.)
 
Hi mpbio,

Thanks for your feedback.

Ok, I will do some consulting internally to confirm that if EULA for
prerequisites can be disabled. I will reply to you ASAP. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi mpbio,

I have got confirmation from product team that the only way to really
bypass this is to not need to install any pre-requisites, in other words,
have them pre-deployed¡­ otherwise, the EULAs are legal requirements and
can¡¯t be hidden.

The bootstrapper is an MSI package (Windows Installer package) that
installs pre-requisites including the .NET Framework which are needed on
the box before the ClickOnce app can run. These are typically machine-wide
potentially impactful installs that ClickOnce is not designed to install.
After pre-requisites are installed the bootstrapper kicks off the ClickOnce
application (launches .application) as the final step.

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top