如何在项目加载时停止Visual Studio 2015连接到每个连接字符串?

Gra*_*ger 10 c# entity-framework visual-studio-2015

尝试打开包含大量连接字符串的解决方案时,Visual Studio 2015会在加载项目时尝试连接到每个连接字符串.

我们团队中的每个开发人员在开发期间都使用SQL Server的本地实例.这个实例可以拥有我们主数据库的多个副本,其中包括不同级别的迁移 - 我们是一个小团队,因此通常最终会在一半时间内完成切换任务.

为了实现这一点,我们有许多特定于机器的连接字符串,在创建DbContext时,我们使用机器名来确定要使用的连接字符串:

<connectionStrings>
  <!-- Steve -->
  <add name="MachineConnection_LT4" providerName="System.Data.SqlClient"
       connectionString="Data Source=LT4\SQL2012;Initial Catalog=xxx;Persist Security Info=True;User ID=xxx;Password=xxx;MultipleActiveResultSets=True" />

  <!-- Sean -->
  <add name="MachineConnection_DESKTOP-UQV58RL" providerName="System.Data.SqlClient"
       connectionString="Data Source=DESKTOP-UQV58RL\SQLEXPRESS;Initial Catalog=xxx;Persist Security Info=True;User ID=xxx;Password=xxx;MultipleActiveResultSets=True" />

  <!-- Sarah -->
  <add name="MachineConnection_Dev-3" providerName="System.Data.SqlClient"
       connectionString="Data Source=Dev-3\;Initial Catalog=xxx;Persist Security Info=True;User ID=xxx;Password=xxx;MultipleActiveResultSets=True" />

  <!-- Graham -->
  <add name="MachineConnection_lt5" providerName="System.Data.SqlClient"
       connectionString="Data Source=.;Initial Catalog=xxx;Integrated Security=True;MultipleActiveResultSets=True" />
  <add name="MachineConnection_graham-surface3" providerName="System.Data.SqlClient"
       connectionString="Data Source=.;Initial Catalog=xxx;Integrated Security=True;MultipleActiveResultSets=True" />
  <add name="MachineConnection_graham-pc-10" providerName="System.Data.SqlClient"
       connectionString="Data Source=.;Initial Catalog=xxx;Integrated Security=True;MultipleActiveResultSets=True" />

  <!-- Alex -->
  <add name="MachineConnection_Dev9" providerName="System.Data.SqlClient"
       connectionString="Data Source=Dev9;Initial Catalog=xxx;Persist Security Info=True;User ID=xxx;Password=xxx;MultipleActiveResultSets=True" />

  <!-- Reuben -->
  <add name="MachineConnection_ReubenPC" providerName="System.Data.SqlClient"
       connectionString="Data Source=REUBENPC\SQLEXPRESS;Initial Catalog=xxx;Integrated Security=True;MultipleActiveResultSets=True" />

</connectionStrings>
Run Code Online (Sandbox Code Playgroud)

然后我们的上下文初始化如下:

public class TTDataContext : DbContext
{
    public const string CacheKey = "dbContext";

    public TTDataContext()
        : base(SqlConnections.GetConnectionStringName())
    {
    }

    ...

}
Run Code Online (Sandbox Code Playgroud)

并使用它来帮助:

public class SqlConnections
{
    private const string DefaultConnectionStringName = "DefaultConnection";

    /// <summary>
    /// Get the name of the connection string to use.
    /// This attempts to find a machine-specific connection string e.g. MachineConnection_LT4, and falls back to
    /// the default connection string if a machine-specific connection string is not found
    /// </summary>
    /// <returns></returns>
    public static string GetConnectionStringName()
    {
        // This enables a connection string to be completely overridden in the cloud service configuration
        try
        {
            var cloudConnectionString = CloudConfigurationManager.GetSetting("TTDatabaseConnectionString");
            if (!String.IsNullOrEmpty(cloudConnectionString)) return cloudConnectionString;
        }
        catch
        {
            // Deliberately empty - an exception will be thrown if not running on AppFabric
        }

        string machineSpecificConnectionStringName = string.Format("MachineConnection_{0}", Environment.MachineName);
        string connectionString = ConfigurationManager.ConnectionStrings[machineSpecificConnectionStringName] == null
                   ? DefaultConnectionStringName
                   : machineSpecificConnectionStringName;
        return connectionString;
    }
}
Run Code Online (Sandbox Code Playgroud)

当Visual Studio 2015加载项目时(初始或更改Git分支),它会尝试建立与列表中指定的每个连接字符串的连接(通过删除除1之外的所有连接字符串来确认),因为它们都是本地的每个相关的机器它会停止响应,直到连接超时,抛出此错误:

SQL连接错误

Visual Studio 2013对此设置没有任何问题.有没有办法说服Visual Studio 2015以相同的方式运行?

Gra*_*ger 7

这是由扩展引起的 - 特别是Karma测试适配器(版本1.1.3),它似乎在项目负载上自动运行一些代码.

禁用此扩展程序解决了该问题.