Public ContosoContext(IConfiguration configuration) Private readonly IConfiguration configuration I did just find a more comfortable way to maintain generating migrations, where you don't have to run the command from the web project.ĭbContext internal class ContosoContext : DbContext Using (var context = new LibraryStoreContext()) Is there a reason why it is returning null if the same connection string worked before following the link to add connection to connectionstring in appsettings? OptionsBuilder.UseSqlServer() īut then it generates the error message on the line optionsBuilder: I did the following: protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) Then it said to change the OnConfiguring() in the Context.cs file that was created.
Options.UseSqlServer(Configuration.GetConnectionString("Default"))) In my appsettings.json file I added ConnectionStrings by doing: ) But on that #warning message, it provided a link which I followed. When I ran the route path to the controller it worked perfectly I was able to see the records from the DB. OptionsBuilder.UseSqlServer("Data Source=DEX-LEP3LOXH0M5\\SQLEXPRESS Initial Catalog=LibraryStore Integrated Security=True") For more guidance on storing connection strings, see. You can avoid scaffolding the connection string by using the Name= syntax to read it from configuration - see. #warning To protect potentially sensitive information in your connection string, you should move it out of source code. In Context.cs file that was created from the scaffolding cmd created this method: protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) I ran the Scaffolding command Scaffold-DbContext "Data Source=DEX-LEP3LOXH0M5\\SQLEXPRESS Initial Catalog=LibraryStore Integrated Security=True" -OutputDir Models.
I created a asp.net core web api project that has, , and.
0 kommentar(er)
