Ready to get started?

Download a free trial of the Salesforce Data Provider to get started:

 Download Now

Learn more:

Salesforce Icon Salesforce ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with Salesforce account data including Leads, Contacts, Opportunities, Accounts, and more!

Access Salesforce Data with Entity Framework 6



This article shows how to access Salesforce 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 Salesforce 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 Salesforce Entity Framework 6 assembly and the connection string.

    There are several authentication methods available for connecting to Salesforce: Login, OAuth, and SSO. The Login method requires you to have the username, password, and security token of the user.

    If you do not have access to the username and password or do not wish to require them, you can use OAuth authentication.

    SSO (single sign-on) can be used by setting the SSOProperties, SSOLoginUrl, and TokenUrl connection properties, which allow you to authenticate to an identity provider. See the "Getting Started" chapter in the help documentation for more information.

    <configuration> ... <connectionStrings> <add name="SalesforceContext" connectionString="Offline=False;User=username;Password=password;SecurityToken=Your_Security_Token;" providerName="System.Data.CData.Salesforce" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.Salesforce" type="System.Data.CData.Salesforce.SalesforceProviderServices, System.Data.CData.Salesforce.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
  4. Add a reference to System.Data.CData.Salesforce.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 SalesforceContext. 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 SalesforceContext : DbContext { public SalesforceContext() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<SalesforceContext>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
  7. Create another .cs file and name it after the Salesforce entity you are retrieving, for example, Account. 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("Account")] public class Account { [System.ComponentModel.DataAnnotations.Key] public System.String Industry { get; set; } public System.String AnnualRevenue { get; set; } }
  8. Now that you have created an entity, add the entity to your context class: public DbSet<Account> Account { set; get; }
  9. With the context and entity finished, you are now ready to query the data in a separate class. For example: SalesforceContext context = new SalesforceContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.Account select line;