Create new Basic Express application (Node.js or TypeScript, same behavior)
Put breakpoint in routes/index.js on line 7:
```
res.render('index', { title: 'Express' });
```
Press F5 to start debugging
Breakpoint should be hit
Press F5
Result: It's going to break again in another index.js, then again, and again. Always on/around line 7.
Comments: Pavel, thanks for attention to remote debugging scenarios. In the following change set used fuzzy logic comparison for remote debugging scenarios only, for local used full file names: https://nodejstools.codeplex.com/SourceControl/network/forks/dtretyakov/debugger/changeset/3a2bfc027d3bd3e4fef99b33d82c4b8da3d92814 But except file name mapping from remote to local for break points required to do that while collecting stack frames and handling exceptions. Also as an additional case for "local" and "fuzzy logic" scenarios we may use file name mapping rules provided by user. It's quite straightforward and has no performance degradation as in "fuzzy logic" case.
Put breakpoint in routes/index.js on line 7:
```
res.render('index', { title: 'Express' });
```
Press F5 to start debugging
Breakpoint should be hit
Press F5
Result: It's going to break again in another index.js, then again, and again. Always on/around line 7.
Comments: Pavel, thanks for attention to remote debugging scenarios. In the following change set used fuzzy logic comparison for remote debugging scenarios only, for local used full file names: https://nodejstools.codeplex.com/SourceControl/network/forks/dtretyakov/debugger/changeset/3a2bfc027d3bd3e4fef99b33d82c4b8da3d92814 But except file name mapping from remote to local for break points required to do that while collecting stack frames and handling exceptions. Also as an additional case for "local" and "fuzzy logic" scenarios we may use file name mapping rules provided by user. It's quite straightforward and has no performance degradation as in "fuzzy logic" case.