1903 results found
In addition to having no trouble getting out to the internet, this machine also has no problem pinging the same server TurboActivate is connecting to: $ ping 104.20.30.216PING 104.20.30.216 (104.20.30.216): 56 data bytes64 bytes from 104.20.30.216: icmp_seq=0 ttl=58 time=66.892 ms64 bytes from 104.20.30.216: icmp_seq=1 ttl=58 time=61.017 ms64 bytes from 104.20.30.216: icmp_seq=2 ttl=58 time=47.256 ms It also has no problem connecting over https, as long as the certificate check is skipped (as the cert for that machine is for *.wyday.com, and as far as I can tell from reverse lookup there's no DNS address attached to that IP): $ wget --no-check-certificate https://104.20.30.216--2016-12-14 23:40:00-- https://104.20.30.216/Connecting to 104.20.30.216:443... connected.
6) Create a new project "MyApp" in wyBuild, 7) create a new local folder "1.0" in which copy all file of my application except my custom wyUpdate8) add all links in "Your program's folder" from the files in local folder "1.0" to the "MyApp" project9) add the address "https:\\mycompanysite.com\mycustomwyupdate\mycustomselfupdate.wys" as host of wyUpdate for "MyApp"10) setting the download site of "MyApp" to "https:\\mycompanysite.com\myapp\%file%"11) build wyUpdate of "MyApp"12 ) build updates and upload "wyserver.wys" and *.wyu file to "mycompanysite.com\myapp\" Question: like before the wyUpdate.exe obtained after the 11) is not the custom wyUpdate.exe, I have to rewrite it before build the update?
update=%25file%25&pkey=%25urlargs%25" rel="nofollow">https://payslipupdate20200310105823.azurewebsites.net/home/LimitUpdate/?
Or just outsource the whole email sending business to a company that does this for a living: http://sendgrid.com/http://mailchimp.com/https://www.google.com/#q=transactional+email&safe=off
(LINK: https://wyday.com/forum/t/3112/automatic-update-not-firing-on-form-load/) I put the AutomaticUpdater control to my WPF app's main window.client.wyc shows that, i'am using version 1.0.0.
See: https://wyday.com/limelm/help/activations/#reactivate >> "Wouldn't the user get the error that all the activations are used up?"
The problem with VMs is that they can be cloned bit-for-bit: https://wyday.com/limelm/help/vm-hypervisor-licensing/ So, as always, you have the choice of whether you want activations and trials to happen in virtual machines.
See https://msdn.microsoft.com/en-us/library/windows/desktop/aa372388%28v=vs.85%29.aspx for a confusing explanation The process is actually far more complicated than my simple explanation.
If it doesn't work, then also tell them to disable the "delayed ACK" feature in Windows: https://support.microsoft.com/en-au/kb/328890 Let me know which fixes things.
Export within a range: Go to advanced search in LimeLM (https://wyday.com/limelm/dashboard/search/ ), select which product keys you want to search for, and then click search.
Note we are currently signing updates following https://wyday.com/wybuild/help/update-signing.php -Does signature also apply to the .wys file?
Get the latest version here: https://wyday.com/limelm/api/ If after updating to the latest version of TurboActivate (currently 4.0.9.6 as of me writing this), integrating it into your app, and trying to reproduce the behavior, if you still see problems with deactivating then we need full step to reproduce and much more information (operating system, operating system version, version of turboactivate, product key causing problems, ability to reproduce, etc.).
More info: https://linux.die.net/man/3/inet_addr Long story short: if you want to be more liberal with your input (and ignore octal addresses), you certainly can, but you'll have to pass the cleaned IP address to TurboActivate.
itemName=PrecisionInfinity.AutomaticVersions#overview" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=PrecisionInfinity.AutomaticVersions#overview- automatically timestamp the AssemblyFileVersion number with the "Date" (yyddd) option. eg: "1.0.25.17278" - "25" is a build number, "17278" is the year "17" & day of the year "278"."
/updates/wyserver.wys">https://www......com/.../updates/wyserver.wys": The underlying connection was closed: An unexpected error occurred on a send.
This is covered in the custom license fields help article: https://wyday.com/limelm/help/license-features/ >> "And I have monthly subscription in my app.
Read more about snake-oil and the purpose of true licensing here: https://wyday.com/limelm/features/why/
Here's how you read changed fields in your app: https://wyday.com/limelm/help/license-features/#change
Incase you run into this in the future, I was successful at utilizing the DesktopBridgeToUWP-https://github.com/Microsoft/DesktopBridgeToUWP-Samples/tree/master/Samples/AppServiceBridgeSample_C%2B%2BI can run your TurboActivation library's outside of the UWP sandbox and handshake back the activation.
I posted my scripts in this post (note that I do not work for Wyday, just a user who uploaded my scripts to help other users): https://wyday.com/forum/t/4270/fastspring-and-saas/ It looks like your scripts are incorrectly modified versions of my scripts.