- If the application binary package is applied on your dev/build environment and this raises the platform build version to be higher than your target sandbox or production environment, you will be blocked from applying any AOT packages that are produced from this dev/build environment. To apply AOT packages produced from a dev/build environment, your dev/build instance must be equal to or lower than your target environments.”
“All Microsoft updates are intended to be runtime backward-compatible. This compatibility covers both binary compatibility and functional compatibility. Runtime compatibility means that customizations that exist in production and sandbox environments will continue to work after Microsoft service updates are deployed to those environments. Those updates include service updates and quality updates. Runtime compatibility also means that Microsoft updates are backward-compatible with customizations that were compiled on an earlier platform.
Binary compatibility is backward only. You can compile a customization on an older application version and platform version, and deploy it to an environment that is running a later version. However, you can't deploy code to an environment that is running a version that is earlier than the version that the code was compiled on.“
So.. this means if I'm running 10.0.35, and I create a new cloud hosted development environment at 10.0.39, update my code, create a Software Deployable Package there, and deploy it to my preproduction and then production environments running 10.0.31, I should receive an error saying I can not do so due te the above warnings.
BUT... when I am doing a Service Update with my Code update it seems I can do my Application AOT code updates (with ISV Code updates to 10.0.39 in this example) and merge the Service Update SDP (10.0.39 from 10.0.35) with the Application SDP created on a 10.0.39 application version cloud hosted environment.
Do I have this right? Any explanation for this behaviour?
Any insights would be appreciated. Thanks so much!