How to manage variable/multiple ConnectionString (Dev and Prod DbContext) in WPF

Question

How to manage variable/multiple ConnectionString (Dev and Prod DbContext) in WPF

Dmtr_Grms 331

I need to manage in a flexible way my ConnectionString, one for DEV and the other one for PROD in order to provide the connection in all my application when needed (create and modify Tables structure, Add/Modify/Delete Record/Reporting.... Today I'm using that ConnectionString in my DbContext definition:

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.UseSqlServer(@"Data Source=xxx\SQLEXPRESS;Initial Catalog=XXXdb;Integrated Security=true;MultipleActiveResultSets=true;");
        }

What should be the best way to manage it correctly and safely? Thanks in advance for your answers. I tried with App.config but connectionstring was not provided for my context.

Dmtr_Grms 331

How it works for me at the moment:

I have in my WPF project a DbModel directory that contains all my tables definition/description as .cs files and 1 XXXDbContext.cs file that contains DbSet,

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.UseSqlServer(@"Data Source=xxx\SQLEXPRESS;Initial Catalog=XXXdb;Integrated Security=true;MultipleActiveResultSets=true;");
        }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        { //Table XXX description and  attributes....
		}

Then in all transaction programs I have :
        // Context initialization
         private readonly AtcDbContext context = new(); 
and Load into EF
                  private void Window_Loaded(object sender, RoutedEventArgs e)         {             // Load the entities into EF Core             context.Accounts.Load();
              // Binding to the source
             accountViewSource.Source = context.Accounts.Local.ToObservableCollection();         } 

Now if I understood well 
1. I should create an appconfig (XML) file?
2. In my XXXDbContext.cs should replace my OnConfiguring with your DbContextFactory
3. In all my transaction programs replace my private readonly AtcDbContext context = new(); with your using (var dbContext = DbContextFactory.CreateDbContext()) is that correct?

Hui Liu-MSFT 48,681 Reputation points Microsoft External Staff

2023-10-09T07:12:30.3666667+00:00

Hi,@Dimitri Garmaise. Is there any update to the question? Has your problem been solved? If so, you could convert the solution that helped you as an answer and accept it. It's helpful for community members with related questions.
Dmtr_Grms 331 Reputation points

2023-10-09T09:35:37.22+00:00

Hi, @Hui Liu-MSFT with pleasure but my question has only comments and no answer, technically I cannot select the right answer...
Hui Liu-MSFT 48,681 Reputation points Microsoft External Staff

2023-10-09T09:44:51.4566667+00:00

Hi,@Dimitri Garmaise. I turned the solution into an answer, you caould accept the solution that is helpful to you as an answer.

Accepted answer

1 additional answer

Your answer

Dmtr_Grms 331 Reputation points

2023-10-06T13:14:19.7333333+00:00

How it works for me at the moment:

I have in my WPF project a DbModel directory that contains all my tables definition/description as .cs files and 1 XXXDbContext.cs file that contains DbSet,

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) { optionsBuilder.UseSqlServer(@"Data Source=xxx\SQLEXPRESS;Initial Catalog=XXXdb;Integrated Security=true;MultipleActiveResultSets=true;"); }

protected override void OnModelCreating(ModelBuilder modelBuilder) { //Table XXX description and attributes.... } Then in all transaction programs I have : // Context initialization private readonly AtcDbContext context = new(); and Load into EF private void Window_Loaded(object sender, RoutedEventArgs e) { // Load the entities into EF Core context.Accounts.Load(); // Binding to the source accountViewSource.Source = context.Accounts.Local.ToObservableCollection(); } Now if I understood well 1. I should create an appconfig (XML) file? 2. In my XXXDbContext.cs should replace my OnConfiguring with your DbContextFactory 3. In all my transaction programs replace my private readonly AtcDbContext context = new(); with your using (var dbContext = DbContextFactory.CreateDbContext()) is that correct?
Hui Liu-MSFT 48,681 Reputation points Microsoft External Staff

2023-10-09T07:12:30.3666667+00:00

Hi,@Dimitri Garmaise. Is there any update to the question? Has your problem been solved? If so, you could convert the solution that helped you as an answer and accept it. It's helpful for community members with related questions.
Dmtr_Grms 331 Reputation points

2023-10-09T09:35:37.22+00:00

Hi, @Hui Liu-MSFT with pleasure but my question has only comments and no answer, technically I cannot select the right answer...
Hui Liu-MSFT 48,681 Reputation points Microsoft External Staff

2023-10-09T09:44:51.4566667+00:00

Hi,@Dimitri Garmaise. I turned the solution into an answer, you caould accept the solution that is helpful to you as an answer.

Answer 1

Hi,@Dimitri Garmaise .Welcome Microsoft Q&A. Not sure about your coding environment and the method you are using. You could try to refer to the following code. If you have any questions please let me know.

App Configuration:

You can store your connection strings in your WPF application's configuration file (App.config or AppSettings.json). Create separate configurations for development and production environments. Here's an example of how you might structure your App.config file:

  <connectionStrings>
    <add name="DevDbContext" connectionString=..." providerName="System.Data.SqlClient" />
    <add name="ProdDbContext" connectionString="..." providerName="System.Data.SqlClient" />
  </connectionStrings>

Create a Factory:

Implement a factory or service to retrieve the appropriate connection string based on your application's environment. You can use conditional compilation symbols or app settings to determine the environment. Here's an example of a simple factory:



public class DbContextFactory
{
    public static YourDbContext CreateDbContext()
    {
        string connectionString;

        #if DEBUG
            connectionString = ConfigurationManager.ConnectionStrings["DevDbContext"].ConnectionString;
        #else
            connectionString = ConfigurationManager.ConnectionStrings["ProdDbContext"].ConnectionString;
        #endif

        var optionsBuilder = new DbContextOptionsBuilder<YourDbContext>();
        optionsBuilder.UseSqlServer(connectionString);

        return new YourDbContext(optionsBuilder.Options);
    }
}

Usage:

Whenever you need to create an instance of your DbContext, use the factory method:

using (var dbContext = DbContextFactory.CreateDbContext())
{
    // Use dbContext for database operations
}

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

you just need the logic to get the connection string where you use it.

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
        string connectionString;

        #if DEBUG
            connectionString = ConfigurationManager.ConnectionStrings["DevDbContext"].ConnectionString;
        #else
            connectionString = ConfigurationManager.ConnectionStrings["ProdDbContext"].ConnectionString;
        #endif

        optionsBuilder.UseSqlServer(connectionString);
}

its more common to inject a dbcontext.

Share via

How to manage variable/multiple ConnectionString (Dev and Prod DbContext) in WPF

1 additional answer

Your answer