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 [dynamic]
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):
| File.ts | Files.ts [dynamic] # |
(#: the second tab is also locked)
It's been awhile now and I can't recall if this is normal, or if I'm missing something?
TS file structure:
Project/
wwwroot/js/ (.js and .js.map files, where 'outDir' points in tsconfig)
Scripts/ (.ts files, and where 'rootDir' points in tsconfig)
Things I already tried and other info:
- Made sure all
.ts
file actions are "TypeScriptCompile". - Verified that the
.map
files correctly point to the source. - The
.js
and.js.map
files are stored together in thewwwroot\js
folder. - The
.ts
files exist in aScripts
folder in the project root. - Right-clicking on the
.ts
file in question under theScript Documents
node during a debug session shows that theURL
referencefile//C:///...pathtofile...
, which is correct (obviously! or it wouldn't be found in the first place) - Made sure script debugging is enabled in IE (not sure that matters for VS, since I think it still works regardless).
- Breakpoints, including the
debugger;
keyword, always break in the dynamic tab and never my opened source tab.
Is this normal behaviour? Thanks.
Specs: Windows 10, Visual Studio 2017, and debugging with IE11.