[FIXED 5.0.17.0] VNCManager upgrade a pain

[FIXED 5.0.17.0] VNCManager upgrade a pain

Home » SmartCode VNC Manager » Bug Reports

http://www.s-code.com/forum/Topic2455.aspx

Print Topic | Close Window

By Lee - Friday, April 03, 2009

Every time I upgrade versions, I have to go dig out my serial number and re-register. It always tells me I have 0 of 14 days left in my trial and won't let me cancel the registration. If I hit the wrong button (which I usually do) VNCManager disappears but it never closes. I have to give it the three-finger salute and manually kill the process.

Am I doing something wrong here?

Vista business, All the current MS updates, 4Gigs RAM.

:Lee

By scottwilkins - Wednesday, August 26, 2009

I agree, it is a pain. I think I can see why this is, to ensure proper licensing.

What I did was to make a .txt file containing the serial in the directory where I store the installable for this application. There is a neat trick that if you copy the serial into Windows clipboard before you start the install, it will autofill the registration when that appears. That's nice at least.

By cconnor - Sunday, September 27, 2009

Just like to add to 2p's worth. I also find this an utter pain the butt and surely completely unnessesery ?

By Yury Averkiev (s-code) - Sunday, September 27, 2009

Well...it's kinda necessary. Scott was correct it's done to ensure proper licensing. We are planning to change the current behavior and implement license checking as a background process. But this will only happens when Xheo.com releases a new major upgrade to their licensing library, which will provide features necessary to implement the background license activation.

By Yury Averkiev (s-code) - Sunday, January 03, 2010

Starting with the 5.0.17.0 build the VNC Manager will remember the registration details. So when you install a new build and run the application the registration window will have all the fields already filled in.

Please note that the 5.0.17.0 will be the first build that will store the registration details. So you will see this feature in action only when you upgrade from the 5.0.17.0 to a newer build.