1900 results found
See: https://wyday.com/limelm/help/api/limelm.pkey.generate/ So really you'll never show any error.
So, the script would accept a product key as a parameter, on the script you'd use the web API to get the product key details (see: https://wyday.com/limelm/help/api/limelm.pkey.getDetails/), and then the script would return that to the calling program (your app).
See all options and a full description here: https://wyday.com/limelm/help/faq/#disabled-adapters Also, TurboFloat *requires* an active network connection (by the very nature of floating licensing).
Our customer is getting internet connection error (TA_E_INET) when trying to activate a verified trial.We have guided them to try instructions described https://wyday.com/limelm/help/faq/#internet-error and it still does not work.
Covered here: https://wyday.com/limelm/help/activations/#deactivate There are lots of options.
At this link I see it's possible to associate named users to a give TurboFloat key: https://wyday.com/limelm/help/licensing-types/#named-user This is nice, but unclear to me is how it works.
On your settings page: https://wyday.com/limelm/settings/ The message will look like: "This API key can only be used from a single IP address per-24 hours.
wyUpdate & AutomaticUpdater are open source, and will remain open source: https://wyday.com/download/ wyBuild is closed source and will remain closed source.
For example, here's C/C++: https://wyday.com/limelm/help/using-turboactivate-with-c-plus-plus/#handle-isgenuinex-correctly Step 3: Don't do a heartbeat check on every startup or even every day.
And, if all else fails, just use the HTTPS communication to bypass poor configuration.
https://imgur.com/a/gNfa0I7 is there a way that can be fixed?
tziaoni wrote:> I'm not sure this is related, but in the past there was a problem with> small file differences, have a look at this topic:> > > https://wyday.com/forum/t/3678/small-change-in-database-not-picked-up-by-wuupdate/ Pretty sure this is the same issue, but the post does not have a relevant solution to the problem :\ But yeah, if the small change adds up to the same value, the change would not be detected by wyupdate during the initial evaluation phase.
And of course, our web API is always available, meaning if you wanted to build your own custom-branded interface for your customers, you can do that too: https://wyday.com/limelm/help/api/limelm.pkey.getDetails/
Our hosted TFS will be on HTTPS. No configuration needed. >> "If a customer's IT department puts all their users behind a proxy server, can users connect from their client machines via the proxy to your hosted TFS?"
Here is https://wyday.com/forum/t/2019/autoupdate-process-hangs/#post-10989 a bug fix in your code.
If you want to extend the trial, see here: https://wyday.com/limelm/help/trials/#extensions
Here's a description of how wyBuild compares versions: https://wyday.com/wybuild/help/faq.php#how-it-works Long story short: either don't add client.wyc to any of the releases, or make sure the latest release always has the client.wyc file.
We describe that in the article, but we don't explicitly tie it to trials: https://wyday.com/limelm/help/vm-hypervisor-licensing/ To disallow VMs in your LimeLM account and use TA_DISALLOW_VM in your app when you use TA_UseTrial().
The better method is to use custom license fields: https://wyday.com/limelm/help/license-features/ Of course that means you have to do a bit more work on the "shopping cart" side.
For verified trials, use either the regular trial extension, or use the offline verified trial request: https://wyday.com/limelm/help/trials/#ut-veri-req >> "Either way, should I assume that extending a trial offline should involve a trial extension key along with UseTrialVerifiedRequest() " No key is needed.