Debugger reports non-existent paths for extracted single-file assemblies

[vitek-karas]

Running a simple console hello world using:

dotnet publish -r win-x64 /p:PublishSingleFile=true /p:IncludeAllContentForSelfExtract=true

Opening the Modules window in VS shows:

Notice the different paths:

• The paths with dzkkvyk3.vi0 actually exist on disk
• The paths with 69f4 don't exist on disk (those files are in the longer folder as well)

Note: In 3.1 single-file ALL files are reported with the "bad" (short) paths, so something in 5 fixed it at least for some files.

Note: Simple self-contained app (non-single-file) doesn't have any problem with this (3.1 or 5)

Tagging subscribers to this area: @agocke, @vitek-karas
See info in area-owners.md if you want to be subscribed.

[vitek-karas]

/cc @VSadov

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.