|
| Iniciado por guest, 22,mar. 2016 23:07 - 7 respuestas |
| |
| | | |
|
| |
| Publicado el 22,marzo 2016 - 23:07 |
Hi Forum,
I have a question regarding live update.
I have a small windev application (WD20) which I woul like to distribute by internet.
I created a live Update installation package, installed it on a rented dedicated server (1&1) and managed to include the live update into an WB page, where the user must register himself to download the WD software.
I am testing it with 4 pilot users, and everything seems to be ok. One user experiences crashes when the live update wants to install a new version, but it works after the second or third attempt.
I have no idea why ..... the other 3 pilots receive the live updates without any problems.
The goal is to distribute this programm to 100+ customers, and I wonder if live update is a stable product ....
So I would be glad, if other user could give me their experience about the live update and its problems, if there any ....
Thanks for your help
Stefan. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2016 - 13:11 |
Hi Stefan
as I had written my own system way before pcsoft live update existed, I've never used it myself. However, according to the posts on the french forum (and google translate is your friend here) it seems it is quite sensitive to a lot of things.
Considering that writing your own system is a 2/3 hours job max, I strongly suggest you do so. A basic system can be done like so:
- a text file contains the information about the last update available. This file never change name/url
- the update itself can be put ANYWHERE (on your server or on any other http accessible server)
- a first httprequest to the text file gets the information, including the url for the update itself)
- if current version<last version (from the text file), a second htprequest can download the update, then a simple shellexecute of it will run it.
If you need to go further than that and circumvent the UAC, because your users do not have admin rigths to install, it is possible to place the wdl in a data directly and update only that.
Of course, after that, you can include a full licence management, and even automatic buying system into this.
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2016 - 15:05 |
Hi Stefan,
I am using live update and it seems to work ok.
The problems I have encountered where:
1. antivirus s/w
2. problems with connections (specially with WIFI)
3. UAC
and in some version - I don't remember which one- my app although it was closed (by the user), it was still running in the background.
Most problems where fixed, after better training of my users (UAC, antivirus) AND
when I stopped installing the application under the programs files directory ..
If you are using a IIs server don't forget to add .net ->text/text in the mime types.
Steven Sitas |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2016 - 21:37 |
Hi Fabrice and Steven,
thanks for your answers
UAC should be a issue, as all customers of this product are business customer,so I except most users will not have admin rights .....
Fabrice, I did not unserstand the meaning of this sentence:
it is possible to place the wdl in a data directly and update only that.
That means you put the WDL in the data directory of the aplication?
I think I will choose Fabrice way, as at the moment the product is new, and I have only this 4 pilots ....., and better investing a few hours more as having trouble with 100+ customers (hoping to get them  )
What I also see with Live Update is a kind of latency .... if I start the application nothing happens for 2 or 3 seconds , which is not really good .....
Thanks
Stefan. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 24,marzo 2016 - 07:28 |
Hi Stefan,
you can split your application in 2 parts:
a launcher (this starts the program, looks for updates and call the component)
the application part (a component *.wdl, your complete appication)
The wdl part can be located anywhere, so in the windows-user- appdata directory.
For the first part you need one time admin rights, for the compoment not. So you must/can update only the second part. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 24,marzo 2016 - 08:27 |
Hi Stefan,
I use the standard out of the box stuff. This works fine for me.
regards
Allard |
| |
| |
| | | |
|
| | |
| |
| Publicado el 29,marzo 2016 - 23:49 |
Hi there,
I installed SSL on the server, and Live Update stopped working ..... I could not figure out why ....
So I took .... as recommended by Fabrice ... a few hours and did my own update procedure ....
Result:
It is faster, it is more easy to install on the server and I have total control about whats going on.
So I am much more happy with my own solution than with live update.
Best Regards
Stefan. |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
34 mensajes |
|
| Publicado el 30,marzo 2016 - 14:50 |
I have been using the Live update for some time. It does work OK but you have to be careful with version numbers.
The original program always tries to update if the version number on the client machine is older than the current version and you have told it to update in these circumstances. You can make it a forced update or just optional (a good idea unless there are data file structure changes). It just looks at the file WDUPDATE.NET for the details of where to look for the update on program start.
To stop it from updating (or if it goes wrong) you just delete WDUPDATE.NET from the program directory. You can then go back and install from the original source.
The only thing I've had problems with were down to local permission issues stopping the download.
--
Regards,
Norman |
| |
| |
| | | |
|
| | | | |
| | |
|