Please split Remobjects SDK 8 remobjects_indy_server_D15 in designtime and runtime packages

[michaelvancann (michaelvancanneytwis)]

Continuing the discussion from Package RemObjects_Indy_D16:

@kdvdt

The package RemObjects_Indy_D16 is a runtime package as well as a designtime package. With this fact it uses the package designide.
This issue makes it unusable under Win64 since there the designide package doesn’t exist.

It would be better to split RemObjects_Indy_D16 into two packages.

As a workaround I will surround the designtime code with a CPUX86 directive.

The same problem exists in the latest Remobjects SDK 8 for Delph XE: The package remobjects_indy_server_D15 depends on the designide package. This prevents people from using run-time packages, since the designide package is not installed (and cannot be installed) on the client’s machine.

Using packages is a requirement for our product.
That means we are currently stuck.

Please do not try to solve this with ifdefs. That is not a correct long-term solution.
The correct solution is to split the package in a design-time and run-time package.

(I am a bit surprised to encounter this bug, because creating separate run-time and design time packages should be Standard Operating Practice for all packages that register components in the IDE.)

[EvgenyK (Evgeny Karpov)]

Just add

{$DEFINE RemObjects_NO_DEMANDLOAD_FIX}

into RemObjects.inc and recompile BuildPackages_D15.groupproj

[michaelvancann (michaelvancanneytwis)]

Hello,

Thank you for the reply.
I found this solution myself, but this should not be necessary.
It can - and IMHO should - work ‘out of the box’, without the need for recompilation.

Please consider a proper solution for the next version.