jaime.rq

I am using ClickOnce, but the application checks for updates by it self, using manual update check. The problem is that if the user doesn't update the application; the next time, when the application starts, it starts like be configure to check for updates before start, so the user get a message from ClickOnce that tells to him that a new version is avaible.
How can I avoid this behavior and configure the application to never checks for new updates automatic.



Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

Oleksiy

Just want to ask you a question:

Did you figure it out

If yes please post the solution here.

I'm doing the same and facing the same problem. :-(





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

jaime.rq

Unfortunately, no.

We think that it¡¯s a bug in ClickOnce technology

What we did was to change the deployment process, we moved to a simple windows installer and we have a xml in a web server that provides the necessary information to know if a new version is available, if it¡¯s we execute a process that runs the setup from a share drive; we uninstall the current version using msiexec /x [package name] /passive and then install the application.

It¡¯s an easy option and you just need some hours to do it.

Key parts:

Read a XML from a url

Parse the XML to a custom object

Verify app¡¯s version

Some backup (optional)

Uninstall the application

Install the new version from a share drive.

I hope that this will be useful for you.
any question just let me know.






Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

David Guyer MS

In the Publish settings, the Updates dialog, you should be able to set the application to Never check for updates. It's the topmost checkbox. Then, your application will rely on your use of System.Deployment (or My.Application.Deployment) to check and download updates.






Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

jaime.rq

that's isn't the problem, the problem is that you configure the deployment as you said, then when you use the client application and an update is available, the application informs that to the user, then if the user skip the update, the next time when the application starts, clickonce checks for a new update like when the application is configure to work as check for updates when application starts.
In simple words, the application change the configuration for no check for updates to check for updates at startup if the user skip to install an update.

Example:
-new app version
-by costum check the app tells to the user that a new version is available
---user skips
-app is closed
-app is start
---during the start up click once behavior is like check for updates at start up
--a window from clickonce tells to the user that a new version is available
Bug! this behavior is incorrect, clickonce should never check for updates at start up if you configure your application to work in that way




Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

Luo

Yepp

Thanks a lot.

I've got the same problem.Before I read this thread it drive me crazy.Does anyone know how to walkthrough it





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

JariNiskala

We are experiencing the same problem. Is the MS development team aware of this problem and if so is this going to be fixed in the next release of VS or .NET

-Jari





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

DevilFish

Has anyone found a workable solution to this problem, or even got any acknowledgement from Microsoft that the problem exists

(Note there is a similar post here: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=562713&SiteID=1, where a number of other people are having the same issue.)





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

jaime.rq

The workable solution I found was the one discribed above, basically emulate the ClickOnce functionality... We have an application in production since Feb-2006 using that method and works fine.

I tried to report the issue to microsoft as a bug, but they turn me their back :( I didn't recieved an email saying anything (like yes it's a bug, or not this is how you could proceed...).


I recomend you to submit the bug report, maybe you get better luck.

ClickOnce is a great technology but it has this big disadvantage.

Regards,
jr




Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

DevilFish

Thanks for the response Jaime, though I was afraid you might say that! I can see how what you suggest would work, but I don't really want to have to write my own ClickOnce. I will try to contact MS directly if I don't receive a useful response from them via this forum, and will post here if I have any luck.



Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

paolog

hi all,

I have the same problem you describe.

Do you know if there are news from Microsoft Developement Team about this bug

Thank you.

Paolo





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

SLang

Hi Guys

I am in the same boat, i think.

I haven't created a custom update yet, i have played around with the auto update and set it to 365 days, i checked for an update and then cancelled. When i restarted the app automatically checked for the update. Future checks were only made after the 365 days had expired. So what i have experienced id that it only checked for an update once after cancelling and then on schedule afterwards (365 days)

With the custom updates, does it only check the once after cancelling or does it look for updates every single time after cancelling

I need control over the updates as they are subscription based, my initial thought would be to use a web service, with the current software version on my server database, to see if a newer version was available and if so and the user wanted to install, then call the update method, this way it would give me the update ability with clickonce.

Any ideas

Regards

Steve





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

SLang

I have created a custom update, after checking for an update and not accepting, when i restart it automatically checks for the update and prompts again. After issuing another update, i do not get an automatic prompt unless i cancel again. Are you guys experiencing the same i.e. only 1 check for an update after cancelling then returning to the custom setting

Rgds

Steve





Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

jaime.rq

Has being a while, if nothing changed since I found the issue it will only check once after you cancel the update; so you are having the same issue I had; the only path I was able to follow was to create a custom implementation and not use ClickOnce. It's very bad that none from Microsoft decided to corroborate the bug and fix it, it's being around since framework 2.0 was released... really bad.

Regards,
jr




Re: ClickOnce and Setup & Deployment Projects Custom Updates Problem

SLang

Jaime, thanks for the reply.

My biggest concern was that it would permanently change my custom settings, but it doesnt.
I dont have a problem with this because the first time my customers look for an update, i have already checked their subscription status using web services.

Rgds

Steve