Release Notes - 2.2

  • 2.2.17
    Moving to LTS.
  • 2.2.17-funcrel
    Fixes a traceback issue present in the analysis log: “AttributeError: ‘NoneType’ object has no attribute ‘scope_parent’”. 📝 48824
    Fixes an issue where an Entity object is linked to the wrong SQL table object. 📝 49011
    Fixes an issue where an Entity name is not resolved resulting in a method being linked to an unknown Entity object. 📝 49013
    Fixes an issue where an Entity operation is not identified when a LINQ ‘where’ method is used without chaining with other LINQ methods.
    Fixes a traceback issue present in the analysis log: “TypeError: Can’t convert ‘NoneType’ object to str implicitly”.
  • 2.2.16-funcrel
    Minor update to ensure the inclusion of success evaluation percentage in analysis log.
  • 2.2.15-funcrel
    Fixes an issue to read the entity table mapping using data annotation. 📝 46790
  • 2.2.14-funcrel
    Designating “DotNet Unknown Entity SQL Query” as a “Data Entity Point”.
  • 2.2.13-funcrel
    This version of the extension is recalled. Please use 2.2.14-funcrel.
  • 2.2.12-funcrel
    “Added new objects for unknown entity and unknown entity operation”.
  • 2.2.11-funcrel
    A new object “Unknown SQL Query” has been added.
  • 2.2.10-funcrel
    Fixes an issue where the links were not created between Entity objects and Database. 📝 44442
  • 2.2.9-funcrel
    Support provided for “table per hierarchy inheritance strategy”.
    Fixed the issue where only the referenced tables participate in the transaction instead of the entity operation objects of the referenced table.
    Vendor property has been introduced for sql query, entity and entity operation objects.
  • 2.2.8-funcrel
    Support provided for EFCore.BulkExtensions CRUD APIs.
  • 2.2.7-funcrel
    Issue rectified for multiple callLinks created in a query involving many select immediate or deferred APIs.
  • 2.2.6-funcrel
    Support provided for all Entity Framework Plus features like Query Cache, Query Future, Query Filter etc.
  • 2.2.5-funcrel
    Support provided for IdentityDbContext for ASP.Net.Support for IdentityDbContext for ASP.Net
    Support provided for CRUD operations through Entity Framework Plus.Support for Entity Framework Plus
  • 2.2.4-funcrel
    Support for APIs: FromSql, FromSqlRaw and FromSqlInterpolated.
    Support for convention for removing pluralization of entity names for tables.
  • 2.2.3-funcrel
    Better recognition of caller methods when connected with the SQL Query objects.
  • 2.2.2-funcrel
    Support has been introduced for ObjectContext APIsSupport for ObjectContext APIs
  • 2.2.1-funcrel
    Support for ExecuteSqlCommand and ExecuteSqlCommandAsync APIs has been provided.Support for ExecuteSqlCommand and ExecuteSqlCommandAsync
  • 2.2.0-funcrel
    Fixes an issue in Entity Framework where, no “Entity Add Operation” got created due to which links were missing from add operation to respective table. 📝 36702
    Fixes an issue where, .NET Entity Operation Objects and links to DB tables were missing. 📝 36625
    Minor improvement in traceback logs.
    Client applications tested.
    Support for Where clauseSupport for Where clause
  • 2.2.0-beta1
    Resolved the issues for missing links 📝 36702
    Missing objects and links in Entity 📝 36625
    Resolution for entity when DBContext.Set<…>() is used for CRUD operations.
  • 2.2.0-alpha2
    EDMX files are read for mapping between entity and table in database, and model first approach.Support for EDMX file
    Support for CRUD operations through DbContext.Support for CRUD operations
    Support for FluentAPI used for overriding default conventions used for mapping entity and table.Support for FluentAPI
  • 2.2.0-alpha1
    The extension is now better able to understand the links between objects by using string evaluation. For example, in this release, the call Links between the caller C# method and the Entity Operation object depicting the CRUD (Create, Read, Update, Delete) function will now be displayed even if the database part has not been delivered. In previous releases this situation would result in the creation of an Entity Object but no link from the client-side C# method to the Entity Object. Now, in this release, because the extension has been improved, an Entity Operation object is created, and a call Link will be created from the client-side C# method to the Entity Operation.Implementation of string evaluation