To lessen the impact to existing customers who do not want to use the new naming conventions and the requirement to change their code, a second interface that duplicates the existing Java conventions has been supplied. This is called the Component Enabler Windows Application Programmatic Interface Java Style (CEWindowsAPIJavaStyle).

With the CEWindowsAPIJavaStyle, there is no need to change the method calls in existing code other than the Component Enabler object creation line in the client code.

With the new interfaces, there is also a new Class Reference Summary document available on AB Suite support website.

The new class reference is much smaller as have hidden classes and methods that were 'public' but could not be used by the client programmer that have been hidden. (They were public to allow access from other runtime environment classes.)

The new interfaces also support Microsoft IntelliSense within Visual Studio. The LINCEnvironment supports the recording capability of the Automated Test Tool (ATT).

It is strongly recommend that you use either of the CEWindowsAPI or CEWindowsAPIJavaStyle interfaces. While it is possible to use the .NET Framework runtime environment directly, it does not have the same level of integration with Visual Studio as either of the interfaces.

The overhead of using the interfaces over using the runtime environment directly is negligible.