You are here

Poweroff Portable Development Test 1

6 posts / 0 new
Last post
englishman
Offline
Last seen: 11 years 3 months ago
Joined: 2010-02-03 11:10
Poweroff Portable Development Test 1

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.

depp.jones
Offline
Last seen: 8 hours 33 min ago
DeveloperTranslator
Joined: 2010-06-05 17:19
Thanks, nice addition

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

  • appinfo.ini: [Details]:Description should be shorter than 236 characters (aim for no more than 150).

Information

  • Suggested file App\AppInfo\appicon_128.png is missing

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:

----------------------------------
keys added:
----------------------------------
HKLM\SYSTEM\ControlSet001\Enum\Root\LEGACY_MPKSLDB7A0BE8\0000\LogConf
HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MPKSLDB7A0BE8\0000\LogConf
(...)
HKU\S-1-5-21-1435418733-1019311667-1915037111-1005\Software\JoBo
(...)
----------------------------------
values added:
----------------------------------
HKLM\SYSTEM\ControlSet001\Enum\Root\LEGACY_MPKSLDB7A0BE8\0000\Capabilities: 0x00000000
HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MPKSLDB7A0BE8\0000\Capabilities: 0x00000000
(...)
----------------------------------
files added:1
----------------------------------
C:\Windows\system32\poweroff.exe

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)

englishman
Offline
Last seen: 11 years 3 months ago
Joined: 2010-02-03 11:10
Thank you... that's really excellent feedback

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.

Gord Caswell
Gord Caswell's picture
Offline
Last seen: 4 days 18 hours ago
DeveloperModerator
Joined: 2008-07-24 18:46
Versioning

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.

depp.jones
Offline
Last seen: 8 hours 33 min ago
DeveloperTranslator
Joined: 2010-06-05 17:19
Good point

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.

Gord Caswell
Gord Caswell's picture
Offline
Last seen: 4 days 18 hours ago
DeveloperModerator
Joined: 2008-07-24 18:46
This particular numbering

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.)

Log in or register to post comments