Constructor not called in .NET Mobilink script

Article ID	1056	Posted Date	9/28/2006
Product(s)		Updated Date	10/10/2006

Problem: When running a Mobilink synchronization script that calls a .NET class you have written to perform the synchronization logic, you may notice that the constructor of your class is never called, causing any references you may have to the Mobilink DBConnectionContext object to be null.

Solution: This situation occurs when your application is using a separate copy of the Moblink script assembly from the Mobilink exe. To resolve this issue, ensure that the Copy Local property is set to false in the properties of your reference to the iAnywhere.Mobilink.Script assembly. You may need to manually delete the local copy of iAnywhere.Mobilink.Script.dll from the bin directory of your assembly.