Hi there, I'm happy to report that my client has reinstated my project that would use advanced installer, so I'm back to trying to figure out the autoupdate mechanism.
I've set up a test EXE which is labeled v1.0.0.0 and created an installer, which worked fine. With that installer I told it to check for autoupdates on my website and filled in the requisite fields.
I then created my v1.1.0.0 EXE, created an installer for it, then created a MSP.
Finally, I created an updates configuration project and filled all that in - pointing to the MSP file. I placed this all up on my server at the specified location, opened the v1.0.0.0 that I had installed and: nothing happened.
I went back through and checked all my paths to make sure they were correctly set up and so far everything checks out. I can hit my updates.txt file here: http://www.steelsphere.com/updates/updates.txt and it is served up properly. I ran the app a couple times, but don't see any requests to my updates.txt file on my web server - so it doesn't look like its checking it at all.
Then I got to thinking that maybe the app won't check again because it had already checked once in the past 24 hours... so maybe it won't check again for another day? Is there a way to force the installer to check for an update? I tried running the updater exe on its own, but it complains about an invalid command line.
Also is there a way to set the autoupdater to check every time the app is launched, instead of only once a day? I can envision a scenario where there is a bug in an update and that even if we released an immediate patch to correct the problem, people wouldn't get it until the next day.
Thanks for your help.
FOLLOW US
Get the latest news in Application Packaging