VOOZH about

URL: https://www.cdata.com/kb/tech/xml-ado-codefirst.rst

⇱ How to Access XML Data Using Entity Framework


How to Access XML Data Using Entity Framework

👁 Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
This article shows how to access XML data using an Entity Framework code-first approach. Entity Framework 6 is available in .NET 4.5 and above.

Microsoft Entity Framework serves as an object-relational mapping framework for working with data represented as objects. Although Visual Studio offers the ADO.NET Entity Data Model wizard to automatically generate the Entity Model, this model-first approach may present challenges when your data source undergoes changes or when you require greater control over entity operations. In this article, we will delve into the code-first approach for accessing XML data through the CData ADO.NET Provider, providing you with more flexibility and control.

  1. Open Visual Studio and create a new Windows Form Application. This article uses a C# project with .NET 4.5.
  2. Run the command 'Install-Package EntityFramework' in the Package Manger Console in Visual Studio to install the latest release of Entity Framework.
  3. Modify the App.config file in the project to add a reference to the XML Entity Framework 6 assembly and the connection string.

    Connecting to Local or Cloud-Stored (Box, Google Drive, Amazon S3, SharePoint) XML Files

    CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.

    Setting connection properties for local files

    Set the URI property to local folder path.

    Setting connection properties for files stored in Amazon S3

    To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:

    • AWSAccessKey: AWS Access Key (username)
    • AWSSecretKey: AWS Secret Key

    Setting connection properties for files stored in Box

    To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.

    Dropbox

    To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.

    SharePoint Online (SOAP)

    To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.

    SharePoint Online REST

    To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.

    Google Drive

    To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.

    The property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

    • Document (default): Model a top-level, document view of your XML data. The data provider returns nested elements as aggregates of data.
    • FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
    • Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

    See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

    <configuration>
     ... 
     <connectionStrings>
     <add name="XMLContext" connectionString="Offline=False;URI=C:/people.xml;DataModel=Relational;" providerName="System.Data.CData.XML" />
     </connectionStrings>
     <entityFramework>
     <providers>
     ... 
     <provider invariantName="System.Data.CData.XML" type="System.Data.CData.XML.XMLProviderServices, System.Data.CData.XML.Entities.EF6" />
     </providers>
     <entityFramework>
    </configuration>
    </code> 
    
  4. Add a reference to System.Data.CData.XML.Entities.EF6.dll, located in the lib -> 4.0 subfolder in the installation directory.
  5. Build the project at this point to ensure everything is working correctly. Once that's done, you can start coding using Entity Framework.
  6. Add a new .cs file to the project and add a class to it. This will be your database context, and it will extend the DbContext class. In the example, this class is named XMLContext. The following code example overrides the OnModelCreating method to make the following changes:
    • Remove PluralizingTableNameConvention from the ModelBuilder Conventions.
    • Remove requests to the MigrationHistory table.
    using System.Data.Entity;
    using System.Data.Entity.Infrastructure;
    using System.Data.Entity.ModelConfiguration.Conventions;
    
    class XMLContext : DbContext {
     public XMLContext() { }
    
     protected override void OnModelCreating(DbModelBuilder modelBuilder)
     {
     // To remove the requests to the Migration History table
     Database.SetInitializer<XMLContext>(null); 
     // To remove the plural names 
     modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
     } 
    }
    
  7. Create another .cs file and name it after the XML entity you are retrieving, for example, people. In this file, define both the Entity and the Entity Configuration, which will resemble the example below:
    using System.Data.Entity.ModelConfiguration;
    using System.ComponentModel.DataAnnotations.Schema;
    
    [System.ComponentModel.DataAnnotations.Schema.Table("people")]
    public class people {
     [System.ComponentModel.DataAnnotations.Key] 
     public System.String [ personal.name.first ] { get; set; }
     public System.String [ personal.name.last ] { get; set; }
    }
     
    
  8. Now that you have created an entity, add the entity to your context class:
    public DbSet<people> people { set; get; }
    
  9. With the context and entity finished, you are now ready to query the data in a separate class. For example:
    XMLContext context = new XMLContext();
    context.Configuration.UseDatabaseNullSemantics = true;
    var query = from line in context.people select line;