The ADO.NET Entity Framework puts more emphasis on the conceptual model by letting developers
programdirectly against it. The ADO.NET Entity Framework conceptual model can be connected directly
to the logical model, providing developers access to the conceptual entities and relationships. It is the job
of the Entity Framework to map entity operations to their SQL counterparts. You can see the benefit of
this: One model can be used across multiple storage engines.
The creation of the mapping between the application and the storage engine is the responsibility of the
ADO.NET Entity Framework. The mapping requires the three parts discussed previously and are created
and used within the application. Three physical components are created in the mapping:
??‘ The conceptual schema definition language (a file with an extension of .csdl).
??‘ The logical storage schema definition language (a file with an extension of .ssdl).
??‘ Themapping specification language (a file with an extension of .msl).
The developer has a couple of options for creating these files.
Pages:
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514