Closed MangelMaxime closed 2 weeks ago
This is just a side effect of the way SourceMaps are written to PDBs and stuff - IIRC changing this would break PDBs, tooling just has to be aware of this and adjust for it. We've had to do it in Ionide, VS handles it, etc. IIRC this comes mostly from the pathmap concept, and it something that is required to be compatible with other tooling.
I indeed read something about pathmap
on this issue https://github.com/dotnet/fsharp/issues/9379
I am not sure if there something to fix or not.
This bug is not too impactful in my situation, as it surfaced because I tried to use EasyBuild.FileSystemProvider in a build project (similar to a MakeFile). So I could disable ContinuousIntegrationBuild
just for the Build.fsproj
if needed.
We are going to close this, as it is not clear how to resolve this issue. If anyone has a specific idea how solve this, feel free to suggest it as a feature improvement for compiler
Hello,
having
ContinuousIntegrationBuild
set totrue
breaks__SOURCE_DIRECTORY__
.Repro steps
Provide the steps required to reproduce the problem:
Create a folder
Minimal
and inside it:Create
Main.fs
withCreate
Repro.fsproj
withRun
dotnet run
and see the reported path be something like/_//Minimal"
If you remove
ContinuousIntegrationBuild
then the reported path is correct.If possible attach a zip file with the repro case. This often makes it easier for others to reproduce. The zip file should ideally represent the situation just before the call/step that is problematic.
Reproduction.zip
Expected behavior
Should report the absolute path even if
ContinuousIntegrationBuild
is setActual behavior
Report
/_/
instead of the actual absolute pathKnown workarounds
None
Related information
Provide any related information (optional):