The real reason you were getting this error is because of the " values in your connection string. If you replace those with single quotes then it will work fine. https://learn.microsoft.com/archive/blogs/rickandy/explicit-connection-string-for-ef (Posted so others can get the fix faster than I did.)
Replace the username and password with Integrated Security=SSPI; So the connection string should be <connectionStrings> <add name=”NorthwindContex” connectionString=”data source=localhost; initial catalog=northwind;persist security info=True; Integrated Security=SSPI;” providerName=”System.Data.SqlClient” /> </connectionStrings>
You need to add a reference to System.Configuration and then use: System.Configuration.ConfigurationManager. ConnectionStrings[“connectionStringName”].ConnectionString;
http://download.oracle.com/docs/cd/B28359_01/java.111/b31224/urls.htm#BEIDHCBA Thin-style Service Name Syntax Thin-style service names are supported only by the JDBC Thin driver. The syntax is: @//host_name:port_number/service_name For example: jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename So I would try: jdbc:oracle:thin:@//oracle.hostserver2.mydomain.ca:1522/ABCD Also, per Robert Greathouse’s answer, you can also specify the TNS name in the JDBC URL as below: jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(PROTOCOL=TCP)(HOST=blah.example.com)(PORT=1521)))(CONNECT_DATA=(SID=BLAHSID)(GLOBAL_NAME=BLAHSID.WORLD)(SERVER=DEDICATED)))
There is a known bug with specifying default command timeout within the EF connection string. http://bugs.mysql.com/bug.php?id=56806 Remove the value from the connection string and set it on the data context object itself. This will work if you remove the conflicting value from the connection string. Entity Framework Core 1.0: this.context.Database.SetCommandTimeout(180); Entity Framework 6: this.context.Database.CommandTimeout = … Read more
You can just do the following: var connection = System.Configuration.ConfigurationManager. ConnectionStrings[“Test”].ConnectionString; Your assembly also needs a reference to System.Configuration.dll
According to Microsoft they are the same thing. When false, User ID and Password are specified in the connection. When true, the current Windows account credentials are used for authentication. Recognized values are true, false, yes, no, and sspi (strongly recommended), which is equivalent to true.