Update Scripting from RegisterType(…) to RegisterByType(…) in AutoCount Accounting version 1.8.21 (147)
Posted on August 4, 2016 | By Daniel Ying
This article applies to AutoCount Accounting Application Script & Plugin.
In order to support many login to AutoCount Accounting on a computer, when multiple BCE.Data.DBSetting instances are created, it is required that the Scripting Registration is to register with the designated instance.
Prior to version 1.8.21, when a class is registered with ScriptManager, there is no requirement to specify which BCE.Data.DBSetting is used.
Script Manager will assume the default BCE.Data.DBSetting instance is being used.
New method to register type of scripting requires to include which instance of BCE.Data.DBSetting.
What happen if customer update AutoCount Accounting to version 184.108.40.206?
The old method remains supported.
However, if your project assemblies reference is updated to version 220.127.116.11, you will see the warning below.
Who needs to update the code to apply RegisterByType(…)?
Every of each plug-in project that has registered for application script is recommended to apply RegisterByType(…).
The reason is any external .net application might initialize your account book, and which in turn will execute your plug-in logic.
If your plug-in project applies RegisterType(…), then your plugin logic might not run on the correct instance in the account book.