title: TypeScript files are loaded in [dynamic] tabs instead of focusing the active source tab
body: <p>In this scenario I have a .Net Core 2 web project, and working on one TypeScript file.  It used to be (if I recall correctly) that errors should break on the opened source tab.  Instead now I'm seeing Visual Studio (2017) break on a NEW tab with the <code>[dynamic]</code> tag next to the tab name; however, the path of this file (when viewing properties) is a file path to the SAME source file I have open! :(  It looks like this (lines are tabs):</p>
  
  <p><code>| File.ts | Files.ts [dynamic] # |</code>
  <em>(#: the second tab is also locked)</em></p>
  
  <p>It's been awhile now and I can't recall if this is normal, or if I'm missing something?</p>
  
  <p>TS file structure:</p>
  
  <pre><code>Project/
         wwwroot/js/ (.js and .js.map files, where 'outDir' points in tsconfig)
         Scripts/ (.ts files, and where 'rootDir' points in tsconfig)
  </code></pre>
  
  <p>Things I already tried and other info:</p>
  
  <ol>
  <li>Made sure all <code>.ts</code> file actions are "TypeScriptCompile".</li>
  <li>Verified that the <code>.map</code> files correctly point to the source.</li>
  <li>The <code>.js</code> and <code>.js.map</code> files are stored together in the <code>wwwroot\js</code> folder.</li>
  <li>The <code>.ts</code> files exist in a <code>Scripts</code> folder in the project root.</li>
  <li>Right-clicking on the <code>.ts</code> file in question under the <code>Script Documents</code> node during a debug session shows that the <code>URL</code> reference <code>file//C:///...pathtofile...</code>, which is correct (obviously! or it wouldn't be found in the first place)</li>
  <li>Made sure script debugging is enabled in IE (not sure that matters for VS, since I think it still works regardless).</li>
  <li>Breakpoints, including the <code>debugger;</code> keyword, always break in the dynamic tab and never my opened source tab.</li>
  </ol>
  
  <p>Is this normal behaviour? Thanks.</p>
  
  <p><em>Specs: Windows 10, Visual Studio 2017, and debugging with IE11.</em></p>