Laz AutoUpdate component - beta

[balazsszekely]

I think you uploaded the wrong zip. I'm downloading from here: https://svn.code.sf.net/p/lazarus-ccr/svn/components/lazautoupdate/latest_stable/updates/lazautoupdate.zip . The package version is 0.2.1.0, but unit versionsuport.pas is the same. Still does not compile with lazarus trunk.

[minesadorada]

I think you uploaded the wrong zip. I'm downloading from here: https://svn.code.sf.net/p/lazarus-ccr/svn/components/lazautoupdate/latest_stable/updates/lazautoupdate.zip . The package version is 0.2.1.0, but unit versionsuport.pas is the same. Still does not compile with lazarus trunk.

Very strange.  I just unzipped lazautoupdate.zip into a new folder, opened Laz1.62/fpc3.0.0 and loaded lazupdate.lpk and clicked 'Compile'.  No errors (see screenshot)

And then with Laz1.7/fpc3.1.1.  No errors (see screenshot)  My copy of 'trunk is Rev:53588M - maybe changes since then?

The Zip is under SVN control, so no versioning issues I think.
What compilation errors are you seeing?

[balazsszekely]

And then with Laz1.7/fpc3.1.1.  No errors (see screenshot)  My copy of 'trunk is Rev:53588M - maybe changes since then?

Yes. LCLPlatformDef was added in Lazarus revision 53711(Dec 8. 2016).

[balazsszekely]

It works here both with 1.6 and trunk. I modified the 0.2.1.0 package. Please test:
http://packages.lazarus-ide.org/test/lazautoupdate.zip

PS: By trunk I mean r. 53941, with r. 53588 won't work.

[minesadorada]

OK. All updated now.  I put in a ForceNotify, but that will be removed on the next Version change.
I'll have to update my copy of Trunk and see the new stuff.  I don't do it often because of the faff of rebuilding the cross-compilers.

Thanks for your help.

[balazsszekely]

OK. All updated now.  I put in a ForceNotify, but that will be removed on the next Version change.

No need for ForceNotify. I will add 0.2.1.0 directly to the main repository. It will be the latest version.

I'll have to update my copy of Trunk and see the new stuff.  I don't do it often because of the faff of rebuilding the cross-compilers.

Yes, this is understandable.

[minesadorada]

LazAutoUpdate Updated to V0.2.2.0

* Support for GitHub added
* You can now host your updates using your GitHub account and have your app update itself.

[lainz]

Many thanks for taking into consideration the GitHub support, I will try it. Is also available in the Online Package Manager right?

Everything is included, also the editor for the zip?

[minesadorada]

Hi Lainz,
V0.2.2.0 is in OPM.
I haven't done the documentation yet, but I'd be grateful if you tested it (I don't use GitHub)
Please follow ALL the steps below:

1. Upload your newer version of the app along with a 'whatsnew.txt' textfile  (together in a zipfile) to a subfolder of 'master'.  The whatsnew.txt file has to be in the zip, and the filename has to be 'whatsnew.txt' else the update won't work.
2. Upload a versionsini file (<name it the same as the app>.ini) in the same location with the format:
; LazAutoUpdate versions file
[versions]
GUI=0.1.0.0

..where the GUI entry is the same as your uploaded app and higher than the app versioninfo you want to update (just recompile it with a lower version for testing)
3. Drop the component onto your GUI form
4. Set the properties:
ProjectType=auGitHubUpdateZip
GitHubProjectName=<your project name in GitHub>
GitHubUserName=<your user name in GitHub>
VersionsININame=<the filename you uploaded in (2)>
ZipFileName=<the filename you uploaded in (1)

Depending on the OS, put the appropriate updater executable updatehmxxx(.exe) in the same folder as your compiled app. (the compiled versions are included in the component directory, else compile them yourself from the supplied source)

Try the methods in the included TestApp or in your own:
LazAutoUpdate1.NewVersionAvailable
LazAutoUpdate1.DownLoadNewVersion
LazAutoUpdate1.UpDateToNewVersion
LazAutoUpdate1.AutoUpdate (which does all of the above, but in one call)

Check out the included TestApp code for a better idea of how to use the methods. It should work for win32 'out of the box' (remember to copy updatehmwin32.exe into the 'compiled' folder)  If it works OK then just change the properties of lazautoupdate1 for your GitHub test.

Long post, but as I said, I haven't done the docs, yet.  Any probs - just post me the properties you used in (4) and I'll test.

[lainz]

Ok seems easy, I will try it.

Just a question, why using master instead of releases?

[minesadorada]

If you work with me, we can probably get it working with releases.  My problem is lack of a test GitHub platform.  I have an old account with just a 'master' repository for testing

Follow the steps for master and test, but also upload testappwin32.ini andtestappwin32.zip to a release, give me the info and I can give it a go.

[balazsszekely]

@minesadorada, @lainz
After you're done with testing and a stable version is ready, I will add it to OPM as default.

[lainz]

If you work with me, we can probably get it working with releases.  My problem is lack of a test GitHub platform.  I have an old account with just a 'master' repository for testing

Ok. I will create a project for testing, I'm not in my PC with all the stuff so maybe in some hours later, first I will try it with the master to ensure that works, and then we can see how to develop it with releases.

[minesadorada]

@minesadorada, @lainz
After you're done with testing and a stable version is ready, I will add it to OPM as default.

Hi GetMem, V0.2.2.0 is still an alpha - I have to add better errorchecking/exception handling in the new code to make it a proper beta.
No hay prisa - I'm done with foobotting and will work on LazAutoUpdate for a bit..

[lainz]

Hi, here is the test project:
https://github.com/lazarusccr/TestLazAutoUpdate

I think I did all the steps right, the application is downloaded but when comes the time to get installed is not happening, I always stay at 0.0.0.0 (the online one is 1.0.0.0). I of course run it as administrator.

Also there's a memory leak somewhere.

The log:

 [2017-01-15 11:57:40.858 Info] Start of Log
 [2017-01-15 11:57:40.858 Info] updatehm version 0.0.15
 [2017-01-15 11:57:40.859 Info] Given parameters follow:
 [2017-01-15 11:57:40.859 Info] App name = testproject.exe
 [2017-01-15 11:57:40.859 Info] Updates folder = updates
 [2017-01-15 11:57:40.859 Info] WhatsNew filename = whatsnew.txt
 [2017-01-15 11:57:40.859 Info] Pretty Name = testproject
 [2017-01-15 11:57:40.859 Info] CopyTree = TRUE
 [2017-01-15 11:57:40.859 Info] Please wait.  Updating testproject....
 [2017-01-15 11:57:40.860 Info] Application path = C:\Users\Damian\Documents\GitHub\TestLazAutoUpdate\bin\testproject.exe
 [2017-01-15 11:57:40.860 Info] Updated application path = C:\Users\Damian\Documents\GitHub\TestLazAutoUpdate\bin\updates\testproject.exe
 [2017-01-15 11:57:40.860 Info] WhatsNew path = C:\Users\Damian\Documents\GitHub\TestLazAutoUpdate\bin\whatsnew.txt
 [2017-01-15 11:57:40.860 Info] Updated whatsNew path = C:\Users\Damian\Documents\GitHub\TestLazAutoUpdate\bin\updates\whatsnew.txt
 [2017-01-15 11:57:40.861 Info] Writing.. whatsnew.txt
 [2017-01-15 11:57:40.861 Info] Waiting 2 seconds...
[2017-01-15 11:57:42.863 Info] Copy to C:\Users\Damian\Documents\GitHub\TestLazAutoUpdate\bin\updates\testproject.exe failed
 [2017-01-15 11:57:42.863 Info] Restarting testproject...
 [2017-01-15 11:57:42.870 Info] End of Log