Calling check method is first step you will perform in
your application update. You must provide URL where it will
connect to download configuration file with list of
files that can and should be replaced.
When it connects to the server, it expects to download
something like this:
#Update file signature
[File]
Name=UpDemo.dll
URL=http://www.weonlydo.com/Update/test/UpDemo.dll
Version=1.0.0.2
[File]
Name=Otherfile.dll
URL=http://www.weonlydo.com/Update/test/file.exe.gz
Version=1.0.2.4
this is plain text file that can be kept on any web
server - no special requirements are needed at all. When
wodAppUpdate parses it, it will see how many files are
available for update and create as many UpdFile objects. You can
access collection of those objects through Files
property.
Besides downloading files, you can have section like
this in same text file:
[Message]
ID=11
Caption=Very important announcement
Text=<HTML><BODY><B>wodAppUpdate</B>
is published!</BODY></HTML>
it can hold admin messages you can show to your users.
You can access those messages through Messages
property.
When Check method completes, CheckDone
event will be fired where you can decide if you will make
changes to downloaded configuration, or just call Download
method to fetch all new files.
Check method will reuse same Proxy settings as they are
defined in Internet Explorer. Also, URL argument overwrites
Login
and Password
properties - keep that in mind.
If you want to see what's happening with
wodAppUpdate and how it decides whether update will be
performed, you can set DebugFile
property to get some debugging information.