Home/ Questions/Q 7640717
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T08:44:24+00:00

I’m trying to use EF 4.3 migrations feature. My ASP.NET MVC project stores connection

  • 0

I’m trying to use EF 4.3 migrations feature. My ASP.NET MVC project stores connection strings in external file:

<connectionStrings configSource="bin\connections.config" />

All runtime procedures (including automatic migrations) work fine. However, no powershell commandlet, connecting to the database, is able to find external file. It throws “Unable to open configSource file” exception. I was trying to place .config file in different places as well as changing configured external file location to no avail. Is there any workaround available?

Update: I’ve found that EF creates a temporary AppDomain with configuration file located in temp directory. So the only workaround at the moment, it seems, is to place external configuration in the same temp directory. Any other suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are unfortunately no easy way to handle external configSource files with the powershell cmd-lets in EF migrations. I’ve given up on it and moved the connection strings into the config file for the class library that contains the db code. The alternative is, as you’ve found out yourself to manually copy the file. Unfortunately the copy process doesn’t honor the build settings of the project, so setting the external config file to be copied at build doesn’t help.

    EF 4.3.1 supports configSource.

    • 0