![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#3
| |||
| |||
|
|
I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#4
| |||
| |||
|
|
I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#5
| |||
| |||
|
|
This isn't the same thing at all. Signing the app simply means that when it comes up with the dialog to install, it says it is from a trusted publisher rather than "Unknown publisher". RobinS. GoldMail, Inc. -------------------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:A33FC30D-2F7A-4D28-90DA-36B5735D69AD (AT) microsoft (DOT) com... I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#6
| |||
| |||
|
|
No. When doing this, trusting the cert, and running from a local Intranet, you get no prompt. It just runs as it should. "RobinS" <robins (AT) imnottelling (DOT) com> wrote in message news:5tmdnTOeGcHVLeDanZ2dnUVZ_qmlnZ2d (AT) comcast (DOT) com... This isn't the same thing at all. Signing the app simply means that when it comes up with the dialog to install, it says it is from a trusted publisher rather than "Unknown publisher". RobinS. GoldMail, Inc. -------------------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:A33FC30D-2F7A-4D28-90DA-36B5735D69AD (AT) microsoft (DOT) com... I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#7
| |||
| |||
|
|
No. When doing this, trusting the cert, and running from a local Intranet, you get no prompt. It just runs as it should. "RobinS" <robins (AT) imnottelling (DOT) com> wrote in message news:5tmdnTOeGcHVLeDanZ2dnUVZ_qmlnZ2d (AT) comcast (DOT) com... This isn't the same thing at all. Signing the app simply means that when it comes up with the dialog to install, it says it is from a trusted publisher rather than "Unknown publisher". RobinS. GoldMail, Inc. -------------------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:A33FC30D-2F7A-4D28-90DA-36B5735D69AD (AT) microsoft (DOT) com... I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#8
| |||
| |||
|
|
Then again, this is via HTTP click once.... not UNC. I don't see why there should be a difference tho. I don't know. "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:OFKqkfoTIHA.536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... No. When doing this, trusting the cert, and running from a local Intranet, you get no prompt. It just runs as it should. "RobinS" <robins (AT) imnottelling (DOT) com> wrote in message news:5tmdnTOeGcHVLeDanZ2dnUVZ_qmlnZ2d (AT) comcast (DOT) com... This isn't the same thing at all. Signing the app simply means that when it comes up with the dialog to install, it says it is from a trusted publisher rather than "Unknown publisher". RobinS. GoldMail, Inc. -------------------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:A33FC30D-2F7A-4D28-90DA-36B5735D69AD (AT) microsoft (DOT) com... I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
#9
| |||
| |||
|
|
I think the prompt he is talking about is when it comes up and says "There is a new version available, do you want to install it?" and lets the user say "Yes" or "Skip". I don't see how adding a certificate would suppress that dialog, nor why you would want it to. Am I misunderstanding the original post? RobinS. GoldMail,Inc. ---------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:OFKqkfoTIHA.536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... No. When doing this, trusting the cert, and running from a local Intranet, you get no prompt. It just runs as it should. "RobinS" <robins (AT) imnottelling (DOT) com> wrote in message news:5tmdnTOeGcHVLeDanZ2dnUVZ_qmlnZ2d (AT) comcast (DOT) com... This isn't the same thing at all. Signing the app simply means that when it comes up with the dialog to install, it says it is from a trusted publisher rather than "Unknown publisher". RobinS. GoldMail, Inc. -------------------------------------- "CMoya" <moy (AT) nospam (DOT) com> wrote in message news:A33FC30D-2F7A-4D28-90DA-36B5735D69AD (AT) microsoft (DOT) com... I'm not sure. But if we're talking about the same thing, I overcame this by signing the app. And then rolling out certificate as trusted via Group Policy. "Mathias Fritsch" <mathiasfritsch (AT) gmx (DOT) de> wrote in message news:87c6aec8-adf5-4ff1-ac6f-57218ba166ea (AT) l32g2000hse (DOT) googlegroups.com... I have set up my clickonce publishing to check for updates on every application restart. The manifest is located on an unc-path. As soon as the user restarts and there is a new version on the Network there is a dialogue with the choice to install the update or not. Is there a way to skip that dialogue? All my clients have to use the new version, if they press "dont install" I am in big trouble. The only way I found was to check manually for updates (ApplicationDeployment.CurrentDeployment.CheckForU pdate()), update the Version (ApplicationDeployment.CurrentDeployment.Update() ) and restart the app (Application.Restart ). But that doesnt look nice. Mathias |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |