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.CheckForUpdate()), update the
Version (ApplicationDeployment.CurrentDeployment.Update() ) and
restart the app (Application.Restart ).
But that doesnt look nice.

Mathias

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" <(E-Mail Removed)> wrote in message
news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>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.CheckForUpdate()), update the
> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
> restart the app (Application.Restart ).
> But that doesnt look nice.
>
> Mathias

Yes, you can push the update as required.

To do this, in the Properties for your main project, in the Publish tab,
click on "Updates...".

Go down to "specify a minimum required version for this application" and
set it to the version you are about to deploy.

When the user next runs the app, it will see that it is a required update,
and will skip the "do you want to update" dialog.

Also note that if you do this, they can not use add/remove programs to
go back one version.

Every time you deploy, you need to change the minimum version.

Hope this helps.
RobinS.
GoldMail, Inc.
------------------------------

"Mathias Fritsch" <(E-Mail Removed)> wrote in message
news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>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.CheckForUpdate()), update the
> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
> restart the app (Application.Restart ).
> But that doesnt look nice.
>
> Mathias

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" <(E-Mail Removed)> wrote in message
news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>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.CheckForUpdate()), update the
>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>> restart the app (Application.Restart ).
>> But that doesnt look nice.
>>
>> Mathias
>

No. When doing this, trusting the cert, and running from a local Intranet,
you get no prompt. It just runs as it should.

"RobinS" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>> 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" <(E-Mail Removed)> wrote in message
>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>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.CheckForUpdate()), update the
>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>> restart the app (Application.Restart ).
>>> But that doesnt look nice.
>>>
>>> Mathias
>>
>

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> No. When doing this, trusting the cert, and running from a local Intranet,
> you get no prompt. It just runs as it should.
>
> "RobinS" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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" <(E-Mail Removed)> wrote in message
>> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>>> 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" <(E-Mail Removed)> wrote in message
>>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>>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.CheckForUpdate()), update the
>>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>>> restart the app (Application.Restart ).
>>>> But that doesnt look nice.
>>>>
>>>> Mathias
>>>
>>
>

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> No. When doing this, trusting the cert, and running from a local Intranet,
> you get no prompt. It just runs as it should.
>
> "RobinS" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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" <(E-Mail Removed)> wrote in message
>> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>>> 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" <(E-Mail Removed)> wrote in message
>>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>>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.CheckForUpdate()), update the
>>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>>> restart the app (Application.Restart ).
>>>> But that doesnt look nice.
>>>>
>>>> Mathias
>>>
>>
>

I agree that there shouldn't be a difference between http or UNC. :-)

RobinS.
------------------------
"CMoya" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> No. When doing this, trusting the cert, and running from a local
>> Intranet, you get no prompt. It just runs as it should.
>>
>> "RobinS" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> 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" <(E-Mail Removed)> wrote in message
>>> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>>>> 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" <(E-Mail Removed)> wrote in message
>>>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>>>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.CheckForUpdate()), update the
>>>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>>>> restart the app (Application.Restart ).
>>>>> But that doesnt look nice.
>>>>>
>>>>> Mathias
>>>>
>>>
>>
>

I think you're right. I misread the post. Apologies.

"RobinS" <(E-Mail Removed)> wrote in message
news:WvOdnfJPx5zYe-(E-Mail Removed)...
>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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> No. When doing this, trusting the cert, and running from a local
>> Intranet, you get no prompt. It just runs as it should.
>>
>> "RobinS" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> 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" <(E-Mail Removed)> wrote in message
>>> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>>>> 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" <(E-Mail Removed)> wrote in message
>>>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>>>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.CheckForUpdate()), update the
>>>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>>>> restart the app (Application.Restart ).
>>>>> But that doesnt look nice.
>>>>>
>>>>> Mathias
>>>>
>>>
>>
>

No problem. He may want to sign his deployment, too.
People tend to get nervous when it says "Unknown publisher"!

RobinS.
GoldMail, Inc.
----------------------
"CMoya" <(E-Mail Removed)> wrote in message
news:0EA2457E-935B-4619-81F9-(E-Mail Removed)...
>I think you're right. I misread the post. Apologies.
>
> "RobinS" <(E-Mail Removed)> wrote in message
> news:WvOdnfJPx5zYe-(E-Mail Removed)...
>>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" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> No. When doing this, trusting the cert, and running from a local
>>> Intranet, you get no prompt. It just runs as it should.
>>>
>>> "RobinS" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> 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" <(E-Mail Removed)> wrote in message
>>>> news:A33FC30D-2F7A-4D28-90DA-(E-Mail Removed)...
>>>>> 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" <(E-Mail Removed)> wrote in message
>>>>> news:87c6aec8-adf5-4ff1-ac6f-(E-Mail Removed)...
>>>>>>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.CheckForUpdate()), update
>>>>>> the
>>>>>> Version (ApplicationDeployment.CurrentDeployment.Update() ) and
>>>>>> restart the app (Application.Restart ).
>>>>>> But that doesnt look nice.
>>>>>>
>>>>>> Mathias
>>>>>
>>>>
>>>
>>
>