Wyatt O'Day (Wyatt) has made 7816 posts.
Are there static libraries available for OS X? Not yet, there hasn't been a demand for them. If yo…
Ok, we'll see if we can squeeze in this feature for the next bugfix release.
Post on Mar 27, 2012So now the question is, how can we parameterize wyUpdate.exe self-updating URL that is presently har…
Post on Mar 27, 2012Hey Alex, You can either manually replace wyUpdate with the newer version, or specify your own sel…
This is odd. Can you reproduce this on any other computers? Did you set any special ACL settings for…
Post on Mar 28, 2012wyBuild version 2.6.17.1. Right, but are you using wyUpdate 2.6.16.4? (Right click wyUpdate.exe, c…
Post on Mar 27, 2012What version of wyUpdate are you using?Are you running as an admin, or as a limited user with "speci…
Just remove the file from the old versions and the new version tabs in wyBuild and wyUpdate will ign…
You also need to recompile your app with the latest version of TurboActivate (2.13 and 3.x are not b…
Post on Mar 27, 2012Hey Karl, The trial extension is not a product key, yet the user is entering the extension into th…
You should consider to include a statement requiring that wyUpdate technology must be referenced in …
Post on Mar 25, 2012We provide tools for developers to make that apps better. This includes updating software (wyUpdate …
There's no way to "undo" TA_SYSTEM setup. And because deactivating is part of the normal user-flow, …
Post on Mar 24, 2012Does this indicate that the admin rights were successfully applied for subsequent calls? Correct.…
Post on Mar 23, 2012The first thing you should do, if you're using PackageMaker, is to set the "Require Admin Authorizat…
I'm a bit confused. When is the crash happening? If you check for updates and there's no updates (an…
Post on Mar 23, 2012First, use the latest version of wyUpdate (2.6.16.4, not 2.6.16.0). Next, after you've given the use…
Thanks David, I'm glad you guys were able to get up and running so fast.
@bergerj We can reproduce your problem. The problem was caused by wyBuild not correctly expanding …
Sure we could do that. In the meantime you can just read the "default value" from the registry node …