TightVNC Viewer Portable 2.5.2 Dev1

The app itself:

• %ProgramData% isn't a valid cross-platform environment variable, it is Win Vista/7 only. You should use %ALLUSERSAPPDATA% instead if files/folders are actually being created there.
• As indicated in the launcher documentation for CleanTemp, did you thoroughly test to ensure nothing is being written to %TEMP%? This is honestly the first app I have looked into that uses CleanTemp.

The post:

• You should include the version number of the app (2.5.1 in this case) in the thread title. This is more important that the development test number in letting people know what version they are getting. The only time you wouldn't include it is for an online installer that always downloads the latest version.
• Not being the previous developer of this you should have started at development test 1.
• Development tests increment in whole numbers only regardless of how major or minor the change, so 3.0.1 should have been 4.
• Dev test number is also reset to 1 whenever you update the base app version.

With the dev test numbering stuff, think of it like this: Here we have TightVNC version 2.5.1. This is the first development test of it, so it is 2.5.1 dev test 1. You update a couple of things in the package, but the base app is the same, so we now have the first revision, thus 2.5.1 dev test 2. If you were then to update the base app (lets say 2.5.4 came out), then you would have the first packaged version of 2.5.4, so it would be 2.5.4 dev test 1.

Also, just because the name of the app doesn't occur elsewhere in the registry or filesystem does not mean other changes haven't been made (you were lucky with TightVNC, but other apps are not as forgiving in their registry/file/folder naming schemes). You should always use an app like RegShot Portable for testing portability.

Those reg entries are fine to ignore as you figured.

As for the potential collision with the TVNC Server, would it be reasonable to handle the non-log files from TVNC Viewer individually, the log files with wildcard substitution, and then use DirectoriesCleanupIfEmpty? Haven't looked that far into it myself, so I don't know whether the files are in their own sub-directories (makes it easy) or not, or if the filenames are in a format specific enough to differentiate server files from viewer files.

NSIS isn't my thing, so no idea how to detect running services, although I expect it is possible.