connection-string

I have the following class in NET Core2.0 App. // required when local database does not exist or was deleted public class ToDoContextFactory : IDesignTimeDbContextFactory<AppContext> { public AppContext CreateDbContext(string[] args) { var builder = new DbContextOptionsBuilder<AppContext>(); builder.UseSqlServer("Server=localhost;Database=DbName;Trusted_Connection=True;MultipleActiveResultSets=true"); return new AppContext(builder.Options); } } This is required in Core 2.0 with migration when Database does not exist and has to be created when you run update-database . Unable to create

I've been trying to edit my connection string for uploading my website to a server. I am not really experienced with this. I got this exception: the Keyword not supported: 'server'. Here is my connection string: <add name="AlBayanEntities" connectionString="Server=xx.xx.xxx.xxx,xxxx;Database=AlBayan;Uid=bayan;Password=xxxxx;" providerName="System.Data.EntityClient" /> I've tried embed this string into my old connection string which works very well locally, but it didn't fit : S For Entity Framework (database-first or model-first; when you have a physical EDMX model file) you need to use a

Is there a utility that will encrypt a named configuration section (or just the connectionStrings section) in an app.config file in a similar manner that one can use aspnet_regiis with web.config files? I know this can be done in code - there are code examples out there, but I am hoping to avoid writing an application for this. RBZ You can try the following: https://magenic.com/thinking/encrypting-configuration-sections-in-net In short - rename the app.config file to web.config - the schema is identical, so aspnet_regiis works. Rename back to app.config when finished. Old question, but here is

Every SQL Server connection string I ever see looks something like this: Data Source=MyLocalSqlServerInstance;Initial Catalog=My Nifty Database; Integrated Security=SSPI; Do I need the Initial Catalog setting? (Apparently not, since the app I'm working on appears to work without it.) Well, then, what's it for? If the user name that is in the connection string has access to more then one database you have to specify the database you want the connection string to connect to. If your user has only one database available then you are correct that it doesn't matter. But it is good practice to put