Summary: This document provides basic information about the extension providing Entity Framework support for C# and VB.NET
Bug fixing only. Please see Entity Framework 1.2 - Bug Fix List.
Improvements have been made to the way exceptions are handled by the extension.
Bug fixing only. Please see Entity Framework 1.2 - Bug Fix List.
This extension provides support for Entity Framework. The calculation of Automated Function Points for your .NET analyses will be supplemented through the creation of new objects and links specific to Entity Framework framework that will link back to objects/links produced by the base .NET analyzer.
In what situation should you install this extension?
If your .NET application contains Entity Framework source code and you want to view these object types and their links, then you should install this extension. More specifically the extension will identify:
- "use" links from Entity Framework objects to participating Database tables
- "rely on" links from C#/VB.NET Classes to Entity Wrapper objects
Entity Framework support
Entity Framework is delivered with the .NET Framework. Therefore the following .NET frameworks are supported by this extension:
|3.0 and above|
'System.Data.Linq.EntityMapping.TableAttribute', 'System.Data.Objects.DataClasses.EdmEntityTypeAttribute', 'System.Data.Objects.DataClasses.EdmTypeAttribute.Name', 'System.ComponentModel.DataAnnotations.TableAttribute', 'System.ComponentModel.DataAnnotations.Schema.TableAttribute' 'System.ComponentModel.DataAnnotations.Schema.NotMapped', 'System.ComponentModel.DataAnnotations.Schema.NotMappedAttribute', 'System.ComponentModel.DataAnnotations.NotMappedAttribute'
Supported methods in fluent api
System.Data.Entity.DbModelBuilder.Entity<TEntityType>() System.Data.Entity.DbModelBuilder.Conventions.Remove<TConvention>() System.Data.Entity.DbContext.OnModelCreating( DbModelBuilder modelBuilder ) System.Data.Entity.ModelConfiguration.EntityTypeConfiguration<TEntityType>.ToTable(String)
Supported tags in .edmx file
<edmx:StorageModels> <EntityType> <Property> </Property> </EntityType> </edmx:StorageModels> <edmx:ConceptualModels> <EntityType> <Property> </Property> </EntityType> </edmx:ConceptualModels> <edmx:Mappings> <MappingFragment> <ScalarProperty> </ScalarProperty> </MappingFragment> </edmx:Mappings>
- Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
- Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
|Quality and Sizing|
CAST AIP release
|8.3.x||C# and VB.NET|
|8.2.x||C# and VB.NET|
|8.1.x||C# and VB.NET|
|8.0.x||C# and VB.NET|
|7.3.7 and all subsequent 7.3.x releases||C# only|
Supported DBMS servers
This extension is compatible with the following DBMS servers:
|CAST AIP release||CSS||Oracle||Microsoft|
|All supported releases|
|An installation of any compatible release of CAST AIP (see table above)|
Download and installation instructions
Include the extension using the interface in AIP Console:
There is nothing further to do. Follow the instructions below to run a new analysis/snapshot to generate new results:
- Modern application onboarding - run the initial deep analysis
- Legacy application onboarding - Step-by-step onboarding - Run the analysis
CAST Transaction Configuration Center (TCC) configuration
In Entity Framework ≥ 1.1, if you are using the extension with CAST AIP ≥ 8.3.x, a set of Entity specific items are now automatically imported when the extension is installed. These items will be available in the CAST Transaction Configuration Center (click to enlarge):
Manual import action for CAST AIP ≤ 8.2.x (optional)
- Locate the .TCCSetup file in the extension folder: Configuration\TCC\DotNet_Entity.TCCSetup
- In the CAST Transaction Configuration Center, ensure you have selected the Templates node:
- This .TCCSetup file is to be imported into the CAST Transaction Calibration Center using either the:
- File > Import Configuration menu option:
- Or right clicking on the Template node and selecting Import Configuration:
- The import of the "DotNet_Entity.TCCSetup" file will provide you with a sample Transaction End point in the Free Definition node under Templates (click to enlarge):
- Now right click the one of the items and select copy:
- Paste the item into the equivalent node under the Application, for example, below we have copied it into the Application MEUDON:
- Repeat the copy / paste process for all items.
Packaging, delivering and analyzing your source code
Once the extension is installed, no further configuration changes are required before you can package your source code and run an analysis. The process of packaging, delivering and analyzing your source code does not change in any way:
- Package and deliver your application (that includes source code which uses the Entity Framework) in the exact same way as you always have. You can refer to the existing official CAST documentation for more information about this - see: http://doc.castsoftware.com/display/DOC83/Source+Code+Delivery+Guide+for+Application+Teams.
- Analyze your delivered J2EE application source code in the CAST Management Studio in the exact same way as you always have - the source code which uses Silverlight will be detected and handled correctly. You can refer to the existing official CAST documentation for more information about configuring an analysis - see: http://doc.castsoftware.com/display/DOC82/2.+Application+Analysis+Process+with+CAST+AIP
What results can you expect?
Once the analysis/snapshot generation has completed, you can view the results in the normal manner. The following objects and links will be displayed in CAST Enlighten:
|Storage Model Table|
|Storage Model Property|
|Public C#/VB.NET class||Rely on||Entity object|
Because CAST cannot be absolutely certain that the C#/VB.NET class is "entity associated", these rely-on links will always be flagged as "dynamic" and will therefore always appear in the Dynamic Link Manager for review.
|Entity object||Use||Database table|
|Class property get/set||Call||Conceptual property |
|Conceptual property||Call||Storage Model Property via Mappping Property|
|Storage Model Property||Use||Database table|
In this section we list the most significant functional limitations that may affect the analysis of applications using Entity Framework:
- Analyzing the participating database tables is mandatory for the extension to work correctly.
- No support for links between LINQ and SQL objects
- Entity Framework objects are not correctly presented in the CAST dashboards
- Enum Collections are not supported.
- DBContexts are not supported.
- Not all Entity Framework and Entity Core namespaces are supported and the analysis log may contain warning about these missing namespaces.