It is difficult to give specific advice on migrating custom written clients, but the following general comments might help the change to using the new .NET Framework runtime environment.

If your client language can use .NET classes directly, then make references to the CEWindowsAPI.dll or CEWindowsAPIJavaStyle.dll. You should then be able to use the new runtime environment directly.

If your client language can use COM classes, then they are likely to be ASP pages, Designing ASP Forms. If your language supports early binding of COM classes, it might be more like the VB6 clients mentioned above.

Generally, the calls are the same regardless of how your client language might access the Component Enabler interfaces. What might be different is the way in which they pass objects back to the LINCEnvironment.

Try the standard methods first, but if you run into problems at runtime on methods that pass objects (such as Connect, Login, Hello and Transaction), try the 'EarlyBind' versions of those methods mentioned in the following section.