Wyatt O'Day (Wyatt) has made 7804 posts.
OK, it sounds like you're using an old version of TurboActivate. Use the latest version (where the e…
Post on Dec 17, 2012If you're talking about using the offline activation option in the TurboActivate wizard, you should …
Yes, but you'd have to put every "target version" in its own separate folder. Which is a huge hassle…
Post on Dec 13, 2012Right now, no. In wyBuild 2.6.x, users can only update to the latest version.
Right now a patch from [OLD version] to [LAtest version] gets built. Meaning you can N+1 new "update…
Here's a list of all the members of the AutomaticUpdater (events, methods, and properties). Set th…
You can tell whether a key is revoked or not by calling limelm.pkey.getDetails and reading the "revo…
OK, we'll try to get that out with TurboActivate 3.3. The schedule's a bit tight right now (we're sh…
Post on Dec 13, 2012OK, this is a pretty old CPU (almost a decade old). Will your app be targeting old CPUs with the ARM…
Post on Dec 13, 2012I think the problem is likely that we're compiling for a newer version of ARM than your board. Looki…
Post on Dec 13, 2012Just to make sure this isn't a bug in JNA (the Java library that make calls to native libraries) can…
We'll look into a better solution to this problem. In the meantime you can use wyUpdate as a standal…
My question is this. If we do not specify an "application data" folder in wyBuild. Will the updater …
About the compilers: Yes, I agree and that is how I build my release version for NASA and for commer…
Post on Dec 11, 2012From the sounds of it this is the same problem you were having before. Namely, the compiler you're u…
If there's no internet then wyUpdate can't check for updates or download the update if it's availabl…
Amazon S3 is pretty popular with people. There are a slew of dedicated VPS's. This is a big question…
Did you call TurboActivate.SetPDetsLocation(); at the top of your app? You should. If you look in th…
You can handle the CloseAppNow event and just don't close your app. But as I said above, the better …
If I try setting it right after InitializeComponent is called (for my window), then setting the prop…