How to Access Vercel Data Using Entity Framework

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 Vercel 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 Vercel Entity Framework 6 assembly and the connection string.

   Using API Key Authentication

   Vercel uses Bearer token authentication. You can use either a personal access token or an OAuth access token as the API key.

   To obtain a personal access token:

   1. Log into your Vercel account at https://vercel.com/
   2. Navigate to Account Settings > Tokens.
   3. Click Create Token, enter a name and expiration, and click Create.
   4. Copy the generated token (it will only be shown once).

   After obtaining your token, set the following connection properties:

   • AuthScheme: Set this to APIKey.
   • APIKey: Set this to your Vercel personal access token or OAuth access token.

   Example Connection String

   Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;
   

   Working with Teams

   Many Vercel resources are scoped to a team. To scope all requests to a specific team, set the TeamId connection property to your team's ID. You can find your team ID by querying the Teams table or from the Vercel dashboard. Alternatively, you can specify TeamId in your SQL queries using the WHERE clause where supported.

   Connecting to Vercel

   Once the authentication is configured, you can connect to Vercel and query data from any of the available tables such as Projects, Deployments, Teams, and Domains.

   <configuration>
    ... 
    <connectionStrings>
    <add name="APIContext" connectionString="Offline=False;Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;" providerName="System.Data.CData.API" />
    </connectionStrings>
    <entityFramework>
    <providers>
    ... 
    <provider invariantName="System.Data.CData.API" type="System.Data.CData.API.APIProviderServices, System.Data.CData.API.Entities.EF6" />
    </providers>
    <entityFramework>
   </configuration>
   </code> 
   

4. Add a reference to System.Data.CData.API.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 APIContext. 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 APIContext : DbContext {
    public APIContext() { }
   
    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
    // To remove the requests to the Migration History table
    Database.SetInitializer<APIContext>(null); 
    // To remove the plural names 
    modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
    } 
   }
   

7. Create another .cs file and name it after the Vercel entity you are retrieving, for example, User. 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("User")]
   public class User {
    [System.ComponentModel.DataAnnotations.Key] 
    public System.String { get; set; }
    public System.String { get; set; }
   }
    
   

8. Now that you have created an entity, add the entity to your context class:

   public DbSet<User> User { set; get; }
   

9. With the context and entity finished, you are now ready to query the data in a separate class. For example:

   APIContext context = new APIContext();
   context.Configuration.UseDatabaseNullSemantics = true;
   var query = from line in context.User select line;