![]() ![]() ![]() 1.4 requires a completely different dll or reference or prerequisite. Lets say version 1.1 is installed, then 1.2 then 1.3. ![]() When I was trying to figure out how to solve this problem, I was under the assumption that specifying a min version would only update apps that are that version or higher. The user will be forced to update (no prompt or choice). You will have to do this every time you publish a new version. The work around is to force the update by checking "Specify a minimum required version for this application" then setting it to the most current version. This (in my mind) would alert them about the update and they could choose to exit the program or update it. I liked the beta (or earlier) screen shots that I saw that also had a check box to "Allow users whether or not to accept the update". The only trouble is if the user is prompted for an update, and chooses to skip the update (whether on purpose or accidentally) they will never be prompted again, until a new update version is published. Make sure you check "The application should check for updates" and "Before the application starts". ![]() As RobinDotNet mentioned, from your Project's property page (and publish tab) you'll have to click on "Updates." to bring up the Updates dialog. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |