Auto actualización de EXE PAR en Windows
Pregunta
Estoy tratando de crear un script que se "volverá a actualizar" cuando detecte una nueva versión en un servidor.Inicialmente, la idea que tuve fue, cuando se detecta una nueva versión, descarga el archivo, luego inicia un archivo DOS BATCH que simplemente sobrescribe el Exe original con el nuevo.Pensé, que podía usar el sytem (Start Update.bat), entonces, inmediatamente, salga de 0;El archivo .bat espera un par de segundos, y luego intenta eliminar el antiguo EXE.Esto falla, supongo, porque incluso cuando se usa el sistema (inicio ...), el nuevo "proceso" es en realidad el mismo proceso, ¿es correcto?¿Hay alguna manera de lanzar un proceso completamente nuevo desde PERL en Windows, eso me permitiría eliminar el .exe?¿O hay un enfoque diferente que sea mejor?
gracias, Eric Seifert
Solución
See the documentation on the Windows Restart Manager, an API introduced with Windows Vista that manages restarting applications, for updates, for you.
Otros consejos
Ever heard of java WebStart? There is a PAR equivalent, PAR::WebStart Basically, you configure it, then download code live from a trusted website
so your .exe would just be a frontend to PAR::WebStart, with the real program downloaded off your website
I know this is an old question, but I thought I'd put my solution here since I'm working on the same sort of thing. Your batch idea is the way I went, but the small change I made was to use exec()
instead of system()
since the former (according to this) "...executes a system command and never returns", which seems to release the running process. This appears to work both when running interpreted Perl files with Strawberry Perl, and when running compiled programs with PAR::Packer
.
I've created test.pl
, which was ultimately compiled to test.exe
, as follows:
#!/usr/bin/perl
use 5.10.0;
use strict;
use warnings;
my $batch_file = <<"BATCH";
rem ### IT IS SAFE TO DELETE THIS FILE ###
\@echo off
ping 127.0.0.1 -n 2 -w 1000 > nul
echo Copying over update file...
copy testfile.exe test.exe
BATCH
open my $fh, '>', 'update.bat';
print $fh $batch_file;
close $fh;
exec( 'update.bat' );
testfile.exe
is a standby "upgraded" version of test.exe
, just to make sure that I can overwrite test.exe
while it's running, and I can. The ping
is a way to pause for 2 seconds to make sure the process has had a chance to exit before trying to overwrite the file.
Oddly enough, the created batch file update.bat
can't delete itself, even though batch files can normally delete themselves. If I create a batch file with this:
start /b "" cmd /c del %0
It will delete itself without any errors. But if I include that snippet in update.bat
, it complains that The process cannot access the file because it is being used by another process.
I'm not sure why. Since this isn't particularly important in my application, I haven't pursued this. I just leave update.bat
behind and let it be overwritten next time an update occurs. But I do notate in the file that it's safe to delete in case anyone looks at it later.