Poweroff Portable Development Test 1
Application: Poweroff
Category: Utilities
Description: (Taken from the link above):
Poweroff is a small program that allows you to control the power state of your pc.
It can power off, shutdown or reboot your pc, log you off, lock your workstation, go to standby or hibernation mode and even wake up another pc.
All actions can be done locally or on a remote pc (if they are running poweroff).
The action can be performed immediately or scheduled, by using a built-in scheduler.
All actions and options can be controlled by command line options. This way, you can easily integrate poweroff in your batch files.
Download Poweroff Portable Development Test 1
[603KB download / 809kb installed]
(MD5: 1c3162b5c735913edf3e454528cc614c)
Release Notes: Development
Test 1 (2011-05-15): Initial release
Points to Note:
Freeware. Permission obtained from author to package:
"Sure you can J"
Full source code and documentation of base application included. Although this is old software it works OK for me on win 7 x64. The base application is already basically portable, but writes registry entries which are now captured.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I did a quick test and found it quite useful. Good work.
Development Toolkit came out clean more or less.
PortableApps.com Format validation passed with 1 warning.
Warnings
Information
I found some issues, but nothing that cannot be fixed.
At first, I missed a proper version numbering. The base app is 3.0.1.3, that should be used in the appinfo.ini, too. The package version should possibly be adjusted to cope with dev test numbering (maybe 3.0.13.0 for dev test 1, 3.0.13.1 for dev test 2).
Then some things are left behind.
Regshot snippet:
Don't know, if the HKLM keys matter. You have some entries in the PoweroffPortable.ini that deal with other HKLM entries. Keep in mind that you need admin rights for that. Adding a RunAsAdmin can help here. That would be needed, too, if you have to deal with the left behind executable in the system32 folder
The enty in HKCU\Software can be dealt with RegistryCleanupIfEmpty (see here)
I wasn't aware of the development toolkit - so I have just found and installed it. I will look at the other issues and hopefully post a new version in a day or two. Thanks.
Dont use a package version greater than the current release. I would recommend the following:
DisplayVersion: 3.0.1.3 Development Test x
PackageVersion: 3.0.0.13x
With x in both being replaced by whatever Development Test you're on, and your official release looking like this:
DisplayVersion: 3.0.1.3
PackageVersion: 3.0.1.3
This allows proper updating of the app, including using the updater if/when this goes official.
That seems plausible. Maybe that such an example could be added to the Format Specification for these cases where the base app uses three separators.
This particular numbering necessitates this. If, for example, you had an application with an original version of 1.3.3.15, your versions here would be:
DisplayVersion: 1.3.3.15 Development Test x
PackageVersion: 1.3.2.15x
Or another example:
Original version: 2.4.1.0 or 2.4.1 (treated same way)
DisplayVersion: 2.4.1.0/2.4.1 (as above) Development Test x
PackageVersion: 2.4.0.99x or 2.4.0.x
Really, it's a matter of personal preference how you do it, so long as versioning always increments up to, but not beyond, an original release.
(Note that a revision of an official release will increment past the original release, by design.)