- #TIGERVNC VIEWER WINDOWS UPDATE#
- #TIGERVNC VIEWER WINDOWS PORTABLE#
- #TIGERVNC VIEWER WINDOWS SOFTWARE#
You should always use an app like RegShot Portable for testing portability.
#TIGERVNC VIEWER WINDOWS UPDATE#
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.Īlso, 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 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. This is the first development test of it, so it is 2.5.1 dev test 1. With the dev test numbering stuff, think of it like this: Here we have TightVNC version 2.5.1.
Dev test number is also reset to 1 whenever you update the base app version. Development tests increment in whole numbers only regardless of how major or minor the change, so 3.0.1 should have been 4. Not being the previous developer of this you should have started at development test 1. The only time you wouldn't include it is for an online installer that always downloads the latest version. This is more important that the development test number in letting people know what version they are getting. You should include the version number of the app (2.5.1 in this case) in the thread title. 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. You should use %ALLUSERSAPPDATA% instead if files/folders are actually being created there. %ProgramData% isn't a valid cross-platform environment variable, it is Win Vista/7 only. Use %ALLUSERSAPPDATA% instead of %ProgramData%, don't save the dir created there, only delete it if it's emptyĭelete web dir that was included with app: it is not included with current distribution of TightVNCĭelete reg key if empty, update Homepage and version Move log files instead of the directory they are in, rename the dir they are saved to in the Data dir to logs, create an App\DefaultData dir add Other/Source directory, as per specifications. If any changes have been made since the last release, they can be viewed at the above link. If TightVNCViewerPortable is opened, then a local copy of an older version of TightVNC Viewer is opened, unknown issues may arise (no tests were done for this scenerio). Basically, the local app will run just like the portable app as long as the portable app is open. If TightVNCViewerPortable is opened, then a local copy of TightVNC Viewer is opened, they will both share the same settings and logs. 
With TightVNC, you can see the desktop of a remote machine and control it with your local mouse and keyboard, just like you would do it sitting in the front of that computer.ĭownload TightVNC Viewer Portable The native viewer now (optionally) supports PiKVM's H.264 encoding. The native viewer is now translated to Romanian and Georgian.
#TIGERVNC VIEWER WINDOWS SOFTWARE#
Description: TightVNC is a free remote control software package. The most prominent changes in this release are: The servers and native viewer now support RealVNC's RSA-AES authentication methods and encryption.
0 kommentar(er)
