When using the latest version of ThinApp - 4.7.2, I recompiled a existing ThinApp (which is a home grown application called MainMenu). We (my work) also has another home grown application (which I'll call AutoUpdate) which uses the ThinApp SDK to basically run the AppSync process in the background for all our ThinApp programs on a laptop so the ThinApp'd programs (we have about 10 so far) stay up to date without actually executing them.
So my problem is that when the latest version, 4.7.2, of my MainMenu program got put out in our AppSync share location, now the AutoUpdate program gives the following error: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
If I take our MainMenu program and recompile the ThinApp with version 4.7.1 the error goes away...this is my current short term fix.
However, long term there is obviously (from my fairly extensive testing) a difference with using the SDK for the AppSync method between the 2 version of ThinApp. I opened a support case with VMware and since the SDK was involved, I was told my only option at this point it to use this forum for support. My biggest concern is now that program is stuck into a particular version of ThinApp and can't move forward, which I think is a bad plan.
So I guess my question is what is different? Will the SDK keep up with the ThinApp progam changes?