title: Visual Studio 2022 can connect to localdb but SSMS 18.10 can't
body: <p>Spanking brand-new installations of:</p>
  <ul>
  <li>Visual Studio 2022 Community (VS)</li>
  <li>SQL Server 2019 Dev (SQL)</li>
  <li>SQL Server Management Studio v18.10 (SSMS)</li>
  </ul>
  <p>There are no other Visual Studio or SQL Server instances or installations.</p>
  <p>A console program creates a localdb database using Entity Framework successfully. VS SQL Server Object Explorer documents this with a connection to <code>(localdb)\MSSQLLocalDB</code> using a connection string of:</p>
  <pre><code>Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=master;
      Integrated Security=True;Connect Timeout=30;Encrypt=False;
      TrustServerCertificate=False;ApplicationIntent=ReadWrite;
      MultiSubnetFailover=False
  </code></pre>
  <p>But I can't get SSMS to connect to this <code>localdb</code> database instance.</p>
  <p>I am trying to use this server name:</p>
  <pre><code>(localdb)\MSSQLLocalDB
  </code></pre>
  <p>What am I doing wrong? I get an immediate (2 second) response with:</p>
  <blockquote>
  <p>The instance of SQL Server you attempted to connect to does not support encryption. (.Net SqlClient Data Provider)</p>
  </blockquote>
  <p>I used sqllocaldb, and everything looks ok:</p>
  <pre><code>sqllocaldb info
  MSSQLLocalDB
  ProjectModels
  
  sqllocaldb info MSSQLLocalDB
  Name:               MSSQLLocalDB
  Version:            15.0.4153.1
  Shared name:
  Owner:              GreenMachine\jean
  Auto-create:        Yes
  State:              Running
  Last start time:    1/21/2022 11:38:11 AM
  Instance pipe name: np:\\.\pipe\LOCALDB#878B8E4E\tsql\query 
  </code></pre>
  <p>So I tried another tack. I pointed my EF connection string to the local SQL Server instance:</p>
  <pre><code> optionsBuilder.UseSqlServer(&quot;Data source = GreenMachine; Initial 
   Catalog=SamuraiAppData; Integrated Security=True; 
   TrustServerCertificate=True;&quot;)
  </code></pre>
  <p>And that worked - I got a new database created on that instance. It seems like SSMS can't connect to localdb!</p>
  <p>Thanks for your ideas!</p>