Infralution Support

RobT · Joined: 09 Apr 2007 Posts: 12

Once an app is registered, I am using GetLicense.ProductInfo.String to display the registered user's name. The user's name was specified as the ProductInfo string when the keys were generated in License Tracker.

The code is simple:

Infralution · Joined: 28 Feb 2005 Posts: 5027

We've just retested this functionality under Vista (both C# and VB source code) without any issues showing up. Some additional information might help us:

Are you including the licensing classes source code in your application? If so is it C# or VB?

How are you generating your license keys (through an ASP.NET server or using License Tracker, License Key Generator)?

What operating system are you generating your keys on?

What version of ILS are you using? Is the source code you are using the same version?

Have you installed the same key on both XP and Vista to verify that the problem is the OS - not the key.

This looks like it might be an encoding issue - does the registered name include non-ascii characters (eg é ç à). Our tests included extended non-ascii characters without any problems - but if you are generating the license automatically (using an ASP.NET server) the problem may be the encoding used to post data to your server app.
_________________
Infralution Support

RobT · Joined: 09 Apr 2007 Posts: 12

I'm using the ILS dll in the application, version 3.4.0.0. The app is a VB.NET app.

I'm generating the keys - at the moment - on XP with License Tracker.

I've installed the key on both XP and Vista in the same version of the application. Only Vista shows this problem. I've tested on both apps by pasting the license key and manually entering it(!) - same difference.

The registered name includes no non-ascii characters.

Rob

Infralution · Joined: 28 Feb 2005 Posts: 5027

Can you email both the problem license key and your validation parameters (from your application code) to support@infralution.com and we will see if we can get to the bottom of it.
_________________
Infralution Support

Infralution · Joined: 28 Feb 2005 Posts: 5027

We done more testing on Vista using different combinations of key strength, product info length and content and haven't been able to replicate any problem. I think we will really need the problem key and validation parameters to get to the bottom of it.

Is the problem happening for every key or just one?
Are you running 32 or 64 bit Vista/XP?
_________________
Infralution Support

RobT · Joined: 09 Apr 2007 Posts: 12

OK, I've emailed you, as requested. Thanks.

Infralution · Joined: 28 Feb 2005 Posts: 5027

Thanks for emailing the product key and validation parameters. I set up a simple project to validate the key. The trailing "f" actually appears in both XP and Vista - the box character that appears in Vista is due to the fact that the product data in the key contains an ASCII code "173" character as the last character. For some reason the .NET framework code that converts the binary data to the string representation:

RobT · Joined: 09 Apr 2007 Posts: 12

I manually entered the product info, so this does open the possibility that I accidentally entered a strange key sequence in addition to the intended product info, but I really don't think that did happen given that I was being especially careful to verify all inputs and outputs, this being the final stage of development and testing.

However, it seems that this 'bug' isn't replicable now: at any rate a newly generated key seems to be handled fine on XP and Vista.

It's a bit disturbing that the .NET framework seems function differently on these two OSes.

I'll keep a close eye on how this behaves and come back if there are continuing anomalies.

I appreciate your support. Thanks.

Rob