Infralution Support

[Blaine Fields]

I use version 2.1.4 and have been reluctant to upgrad because I have modified and adapted the source code. The process works well for PDAs running WM 2003 and WM 5.0. However, I have run into a problem with WM 6.0.

The LicenseMonitor will correctly report on the initial use of my software that "you are on day 1 of the 30 day evaluation period." After closing the program and restarting, the LicenseMonitor.DaysInUse value is returned as "733242" and the LicenseMonitor.Invalid value is "true". This does not happen in WM 5 and lower installations so I am assuming it is a registry problem.

I'd like to avoid the hassle of dealing with upgraded code if at all possible. Can you suggest a modification to the current code to make it behave with respect to WM 6?

Thanks.
_________________
Blaine Fields

[Infralution]

There have been a few fixes affecting EvaluationMonitor since 2.1.4 (see the Release Notes for details). I notice that you have deceided to upgrade - has this fixed the issue for you? If not let us know.
_________________
Infralution Support

[Blaine Fields]

I went ahead and purchased the upgrade anticipating that the fix would be more than a few tweaks. However, I did try to implement the UInt16 to Int32 changes for the SerialNo that I saw in the Release Notes and found that my license key had ballooned from 32 characters to 48, an undesirable result. So I returned the code to its original and decided to wait to see what you had to say about the problem.

If there is a discreet issue that can be corrected to insure access to the WM 6 registry, perhaps you could tell me what it is. It is interesting that the problem seems to be limited to the writing and/or reading of the DateTime information. Getting the check sum is not a problem so when the user enters the license key the program runs just fine which means that it is retrieving the check sum data from the registry without a problem.

Before I upgrade, any advice?
_________________
Blaine Fields

[Infralution]

[Blaine Fields]

Thanks for the above, I'll check it out and see what I did.

Regarding the WM 6 problem, I have discovered what the problem really is and it is an odd one. Let me preface this by saying that I prefer a date format like DD MMM YY, so today's date is 22 Jul 08. When setting up my PDA test bed, I specify that format but also have to change the separator from a dash to a space. Follow so far? Instead of "22-Jul-08" I like "22 Jul 08."

In the GetDateData function called in the Evaluation Monitor the date of first use is obtained from the registry without a problem and the string looks like "19 Jul 08 17:51:28". Next the DataTime.Parse (dateString) function is called. It seems not to be able to parse that string. This is where the exception is thrown and the invalid parameter becomes true. However, and this is where it gets odd, if I change the PDA so that the dash is used as the separator, there is no problem parsing the SAME string. Note that the date string does not change, but somehow the DateTime parser works properly when the dash separator is specified even though there are no dashes in the date string.

Every now and then a user of my software will report that the evaluation period expires after the first use and this could be the reason. Any ideas?
_________________
Blaine Fields

[Infralution]

I think you will find that this issue has been fixed in Version 3 of the EvaluationMonitor code. The code now stores the date in an invariant culture format. Let us know how you go.
_________________
Infralution Support

[Blaine Fields]

Thnks so much for your patient help. Everything seems to be working now - and, while I didn't implement all of the updated code, I implemented enough to get rid of the OpenCF file which reduced the size of the compiled file by 75%.

Thanks again.
_________________
Blaine Fields