Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 784921
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T20:47:26+00:00 2026-05-14T20:47:26+00:00

We have a WPF application deployed using ClickOnce which checks for and performs updates

  • 0

We have a WPF application deployed using ClickOnce which checks for and performs updates programmatically on application startup. This generally behaves perfectly except for the case where the user chooses “No” to our “Do you wish to update?” prompt. In this case, the next time the user launches the application (consistently) the ClickOnce framework’s “Update Available” dialog launches with the option to update or skip. This doesn’t cause a technical problem but will be confusing to the user to potentially see two completely differently styled dialogs. (If the user chooses Skip to the ClickOnce dialog then the application then launches and renders our own “Update Available” dialog). Any ideas why the ClickOnce framework dialog is showing in this case? Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T20:47:27+00:00Added an answer on May 14, 2026 at 8:47 pm

    In the Updates dialog (which is in the Publish tab), do you have the boxes unchecked for checking for updates?

    [EDIT 6/18/2010] Here’s some more information that I think will fix your problem.

    The CheckForUpdate() and CheckForDetailedUpdate() methods persist the results of the update check to disk.  The next time the application runs, the ClickOnce mechanism sees that an update is available and prompts the user with the unwanted window.  

    Apparently the update is a two step process:

    • Step 1 – Check the deployment location for updates and persist the information about what it finds to the local ClickOnce update cache.
    • Step 2 – Check the local ClickOnce update cache and prompt the user with the update window if there an update is indicated.

    Unchecking “The application should check for updates” option seems to only cause ClickOnce to skip Step 1.  Step 2 still occurs.  

    The CheckForUpdate() and CheckForDetailedUpdate() methods have the same effect as Step 1 – the data is persisted to disk, so the next time the application is run, Step 2 sees the update and displays the update window.  

    The trick is prevent CheckForUpdate() and CheckForDetailedUpdate() from persisting this information to disk.  This can be done by using the parametered overload (CheckForUpdate(bool persistUpdateCheckResult) or CheckForDetailedUpdate(bool persistUpdateCheckResult)) with the parameter set to false (that is, CheckForUpdate(false) or CheckForDetailedUpdate(false)).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 434k
  • Answers 434k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Pick your particular "NoSQL" database first -- or at least… May 15, 2026 at 3:21 pm
  • Editorial Team
    Editorial Team added an answer Using the answer provided here: Caret position in textarea, in… May 15, 2026 at 3:21 pm
  • Editorial Team
    Editorial Team added an answer It is just really tough to tell exactly what you… May 15, 2026 at 3:21 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.