We are midway through moving from adTempus 2.x to 3 and we have run into an issue with executing "helper" programs written utilizing the 2.0 API, for example:
Dim engine As ArcanaDevelopment.adTempus.Server.Engine
Dim session As ArcanaDevelopment.adTempus.Server.ApplicationIntegration
Are there any hints for supporting these .NET executables under adTempus 3? We were hoping not to have to rebuild and retest these utility programs.
Thanks but I gave up and recompiled the executables for the 3.0 DLL; we'll just continue with the testing cycle.
In future please create a new topic rather than posting in an unrelated old topic. I have moved your posts to a new topic.
As you have found the migration from 2.x to 3.x does involve some API changes and it is necessary to rebuild your client applications. Other changes may be necessary: most importantly, indexing of collections changed from 1-based to 0-based. See the Changes in Version 3.0 topic in the API documentation for more information.
Note that version 4 is coming soon and it has more substantial changes to the API, hopefully for the last time. Rather than migrating to version 3, you may want to consider going directly to version 4, either now using the beta, or later this year when it releases. Unfortunately documentation on the API changes for version 4 has not been completed yet, but there is preliminary API documentation available here.
Replies are disabled for this topic.
Staff