Release Notes - 1.1
1.1.0-funcrel
Fixes/Bugs
Customer Ticket Id | Technical Details | Customer Details |
---|---|---|
Fix problem with returning correct value of procedure from a MemberAccess type of value. | Fix problem in value conversion to return correct object. | |
Fix issue in method that filters string value to determine if the current string can be considered unknown. | Fix error where known objects were filtered into unknown objects. | |
Resolve an issue where a maximum recursion depth error was triggered while resolving collection or database objects. | Enhance configuration of internal library. | |
Add support for LINQ to SQL from ADO.NET to also fix the issue of missing object in this ticket. | Add new support for LINQ to SQL from ADO.NET. This results in creation of new objects. | |
Unknown object created instead of a known object, from a supported callback ==> add better heuristic and string conversion to handle the missing case of string.join | Resolved an issue that caused an error during API callback. The fix results in the creation of correct known object. |
New Support
Customer Ticket Id | Technical Details | Customer Details |
---|---|---|
Add new property TriggeredBy to callLink between real caller and the custom objects created by Dotnet Ado. | Full name of the API responsible for executing CRUD operation or data query can now be viewed in the call link. | |
Following the new added support for LINQ to SQL, the past supports for SQLiteNet had also been updated to match the new modelisation of ORM. Callbacks those match ORM models had been updated to created Entity - Entity Operation objects | Update past support of SQLiteNet to some callbacks, from creating SQL Query to Entity Operation object | |
Add support for LINQ to SQL syntaxes in ADO.Net, consisting system.data.linq and system.linq ==> new types of objects are created: Entity, Entity operation and their unknown counterparts | Add support for LINQ to SQL following ORM modelisation. |