IW10 open IW14 Form (dll)

[alex.trejo@tttnet.com.mx]

Hi,
We are preparing to migrate a large D2009/IW10 isapi application to a more recent dev environment (10.2.3/IW14.2.6 which we already have or possible go to IW15).
We would like to have the possibility to keep the current IW10 app as entry point, create a new IW14 dll that could be referenced from IW10 app and where we have migrated and new forms. So, when we have a new form migrated, we call the new IW14 version from within the IW10 app. Is something like this possible with IW? When I In VCL it is possible to include an external dll library which opens new forms, but when trying it in IW it throws AV.

How can we accomplish this? We want to keep/pass user information from IW10 app to IW14 forms.
Thanks
Alex

The problem is how to share the session state (internal session data, like "what's the logged user?). It is feasible if you program your application like it was a REST server (i.e. each request does one unique thing an that's it, no complex stuff depending on transactions, etc.)
Otherwise I recommend you to migrate it completely.

Alexandre,
I totally agree that a full migration is the best approach. We are actually working on it as a parallel project. However, due to the size of the IW10 application and the urgency to add some functionality/forms that require Async capabilities not available in IW10, we need to consider this mixed environment. Being able to add a dll library in IW14 with new forms/funtionality to the IW10 app would have provided a very usefull middle ground (forms/funcionality in that dll library would serve to both actual IW10 app and migrated IW14 project), not having to control info passing to and from 2 apps. The app is not a REST server, that is why I don't see how to provide with the "back" communication, other than the calling app constantly polling database, which is undesirable. Thanks for your comments, I appreciate very much the support of such giants as yourself and Kudzu.