I forgot to say.
Please, build a WPKGClient .msi installer that are able to upgrade
itself as soon as possible, i think this is the real priority now,
new features will come. ;)
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia''
Marco Gaiarin schrieb:
I forgot to say.
Please, build a WPKGClient .msi installer that are able to upgrade
itself as soon as possible, i think this is the real priority now,
new features will come. ;)
It should be able to upgrade itself, provided you have Windows Installer
3.1 installed.
Marco Gaiarin schrieb:
Mandi! Tomasz Chmielewski
In chel di` si favelave...
It should be able to upgrade itself, provided you have Windows Installer
3.1 installed.
Doesn't it work for you?
I meant: release please a fixed 1.2.X version, or release 1.4.0 without
loosing too much time
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and even
after wpkg was done with everything I cannot
Jens Geile schrieb:
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and even
after wpkg was done
Mandi! Tomasz Chmielewski
In chel di` si favelave...
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and
even after wpkg was done with everything I cannot start the service again
for like 2
Mandi! Tomasz Chmielewski
In chel di` si favelave...
I think it should also upgrade if you have Windows Installer 3.1, but I
didn't test it personally.
You are saying that 1.2.X just works?
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and
even after wpkg was done with everything
First off I'd like to thank the developer(s) of WPKG for all the hard work
they've put into this. WPKG has proven to be extremely useful for a network
I'm currently setting up.
Recently while I was setting this network and WPKG up, I thought it would be
nice to have a message window of sorts
