How to point the Entity framework to another database?

Question

How to point the Entity framework to another database?

Asked 8 years, 9 months ago

Viewed 533 times

3

Hello,

My Entity Framework always points to my local database...I have tried to change the string Connection by passing the data of a database that is on another server and nothing happens it keeps pointing location even if I comment the connectionString

<add name="DefaultConnection" providerName="System.Data.SqlClient" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-ProjetoZeus-20151023162720;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-ProjetoZeus-20151023162720.mdf" />

Does anyone know how I can fix this ?

Complete Web Config:

<?xml version="1.0" encoding="utf-8"?>
<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=152368
  -->
<configuration>
  <configSections>
    <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />  
  <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
  </configSections>
  <connectionStrings>
    <add name="DefaultConnection" providerName="System.Data.SqlClient" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-ProjetoZeus-20151023162720;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-ProjetoZeus-20151023162720.mdf" />

  </connectionStrings>
  <appSettings>
    <add key="webpages:Version" value="2.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="PreserveLoginUrl" value="true" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
  </appSettings>
  <system.web>
    <httpRuntime targetFramework="4.5" />
    <compilation debug="true" targetFramework="4.5" />
    <authentication mode="Forms">
      <forms loginUrl="~/Login/Index" timeout="2880" />
    </authentication>
    <pages>
      <namespaces>
        <add namespace="System.Web.Helpers" />
        <add namespace="System.Web.Mvc" />
        <add namespace="System.Web.Mvc.Ajax" />
        <add namespace="System.Web.Mvc.Html" />
        <add namespace="System.Web.Optimization" />
        <add namespace="System.Web.Routing" />
        <add namespace="System.Web.WebPages" />
      </namespaces>
    </pages>
    <profile defaultProvider="DefaultProfileProvider">
      <providers>
        <add name="DefaultProfileProvider" type="System.Web.Providers.DefaultProfileProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" applicationName="/" />
      </providers>
    </profile>
    <membership defaultProvider="DefaultMembershipProvider">
      <providers>
        <add name="DefaultMembershipProvider" type="System.Web.Providers.DefaultMembershipProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" />
      </providers>
    </membership>
    <roleManager defaultProvider="DefaultRoleProvider">
      <providers>
        <add name="DefaultRoleProvider" type="System.Web.Providers.DefaultRoleProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" applicationName="/" />
      </providers>
    </roleManager>
    <!--
            If you are deploying to a cloud environment that has multiple web server instances,
            you should change session state mode from "InProc" to "Custom". In addition,
            change the connection string named "DefaultConnection" to connect to an instance
            of SQL Server (including SQL Azure and SQL  Compact) instead of to SQL Server Express.
      -->
    <sessionState mode="InProc" customProvider="DefaultSessionProvider">
      <providers>
        <add name="DefaultSessionProvider" type="System.Web.Providers.DefaultSessionStateProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" />
      </providers>
    </sessionState>
  </system.web>
  <system.webServer>
    <validation validateIntegratedModeConfiguration="false" />
    <handlers>
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" />
      <remove name="ExtensionlessUrlHandler-Integrated-4.0" />
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" path="*." verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv4.0,bitness32" responseBufferLimit="0" />
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" path="*." verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv4.0,bitness64" responseBufferLimit="0" />
      <add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
    </handlers>
  </system.webServer>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="EntityFramework" publicKeyToken="b77a5c561934e089" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="WebGrease" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
    <providers>
      <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
    </providers>
  </entityFramework>
</configuration>

Class that inherits Dbcontext

public class Contexto : DbContext
    {
        public DbSet<Cliente> Clientes { get; set; }
        public DbSet<Produto> Produtos { get; set; }
        public DbSet<Pedido> Pedidos { get; set; }
        public DbSet<Usuario> Usuarios { get; set; }
        public DbSet<Pais> Paises { get; set; }
        public DbSet<Estado> Estados { get; set; }
        public DbSet<Cidade> Cidades { get; set; }
        public DbSet<Fornecedor> Fornecedores { get; set; }
        public DbSet<Endereco> Endereco { get; set; }
        public DbSet<ItemPedido> Itens { get; set; }

    }

context:

Contexto context = new Contexto();

Pole the web.config or app.config complete.

– Jéf Bueno

2015/12/10 at 18:39
edited in the question

– Daniel

2015/12/10 at 18:41

3 answers

Browser other questions tagged .net sql-server entity-framework

You are not signed in. Login or sign up in order to post.

by Leonel Sanches da Silva • **88,623** points · Answer 1 · 2015-12-10T18:45:17+00:00

2

Not much of a secret. Pro SQL Server, for example, just point to the instance and remove the reference to the file name, because traditional SQL Server databases do not use files:

  <connectionStrings>
    <add name="DefaultConnection" providerName="System.Data.SqlClient" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=ProjetoZeus;Integrated Security=SSPI;MultipleActiveResultSets=True" />
  </connectionStrings>

Here I am considering that you have installed SQL Server Express.

Gypsy...I want to point to a new Amazon server that I just caught... wanted him to create the automatic tables... Code First

– Daniel

2015/12/10 at 18:48
If Amazon created the database for you, yes, you need.

– Leonel Sanches da Silva

2015/12/10 at 18:51
I commented the connectionString that was pointing location and put another according to the one you sent...but still pointing local rs

– Daniel

2015/12/10 at 18:55
There’s something wrong there. You didn’t happen to force a Connection String in the DbContext?

– Leonel Sanches da Silva

2015/12/10 at 18:58
worse than not...

– Daniel

2015/12/10 at 19:02
Very weird. It’s all right. See how it looks web.config after publication.

– Leonel Sanches da Silva

2015/12/10 at 19:05
web.config ta equal to the top ai...only ta different here <connectionStrings> <!-<add name="Defaultconnection" providerName="System.Data.Sqlclient" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-ProjetoZeus-20151023162720;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-ProjetoZeus-20151023162720.mdf" />-->
 <add name="DefaultConnection" providerName="System.Data.SqlClient" connectionString="Data Source=. SQLEXPRESS;Initial Catalog=Projecteus;Integrated Security=SSPI;Multipleactiveresultsets=True" /> </connectionStrings>

– Daniel

2015/12/10 at 19:09
Well, I don’t know what it is. I still think it’s some configuration thing.

– Leonel Sanches da Silva

2015/12/10 at 19:10
It’s too weird ne

– Daniel

2015/12/10 at 19:11

Show 4 more comments

by Randrade • **21,612** points · Answer 2 · 2015-12-10T20:35:48+00:00

As you said in the comments you’re pointing to an Amazon server, I don’t know if it’s the same as your application, but try using this connectionString:

<add name="DefaultConnection" connectionString="Data Source=SERVER\INSTANCIA;Initial Catalog=DATABASENAME;Persist Security Info=True;         User ID=USUARIO;Password=SENHA;MultipleActiveResultSets=True"providerName="System.Data.SqlClient" />

At this link has several examples for connectionStrings.

by Warley Ferreira Silva • 11 points · Answer 3 · 2016-12-29T12:20:02+00:00

-1

If your application is layered it may be that in the persistence layer you have an app.config file with an additional connection string. This happens in some cases depending on how you created the model.

It may be that this is always forcing the note to the local bank.

Dude, blz. I just started my account and I didn’t know that the community was just for veterans, and I don’t even think that community is built like this. Besides, from what I analyzed of the question I really believe that this might be it, an extra connection string in the app.config that the guy might not have realized existed, was an attempt to help someone solve a problem, After all the guy just asked how to change the database his application is pointing to, because even commenting the string on the web.config application continued pointing to the local bank, would not need more information.

– Warley Ferreira Silva

2016/12/29 at 16:10