Our application has recently moved to version 2.0.20073.61130 of C1.Win.C1TrueDBGrid.2.dll.
Since then, we have noticed a 25 second delay whenever this DLL is initially referenced from the deployed application. Subsequent references from the same application process behave as expected..
The application is built in Visual Studio 2008 on Windows XP Professional (SP2), and the issue does not occur on developer machines.
The issue only manifests itself when the application is deployed to a Terminal Services environment running under Windows Server 2003.
The DLL is included in the same directory as the application executable, both of which are copied to the deployment server and run directly with no additional installation procedures.
In attempting to resolve the issue, we have added the TrueDBGrid DLL to the GAC and used NGEN to cache a native version of the library. Both efforts have had not improved the delay.
The Grid is created at run-time, but the application's 'licenses.licx' file contains the correct reference and Public Key Token.
This is repeatable outside of the application, and a separate Test Harness has been created which encapsulates the issue. The delay occurs when entering a procedure that creates a new instance of the grid, but before the New declaration is called.
As well as copying to the deployment server as above, the Test Harness has been published as a formal application. The issue remains after installing this formal application on the deployment server.
We have attempted reference redirection from the Test Harness to an older version of the library; 2.0.20053.51105. This removes the delay, but presents the licensing splashscreen as expected when attempting to create a New instance of the grid. We would prefer not to have to do this in the full application.
Upon further testing, the 25-second delay occurs whenever any of the C1 libraries from build 20073 are referenced, not just TrueDBGrid.
Please let me know if there are any methods that we could use to resolve this issue.
If any other information is required, such as sample code from the Test Harness, we will be happy to oblige.
Regards,
Daryl Parson