06-30-2020, 12:11 AM
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
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