We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fsc deletes the output directory when the --out flag is set to a rooted path and the compiled script contains NuGet references.
fsc
--out
Repro steps
Provide the steps required to reproduce the problem:
FROM mcr.microsoft.com/dotnet/sdk:6.0.100-preview.7-alpine3.13 WORKDIR /repro RUN echo "#r \"nuget: FSharp.Data, 4.2.2\"" > ./script.fsx && \ dotnet /usr/share/dotnet/sdk/6.0.100-preview.7.21379.14/FSharp/fsc.dll \ -a script.fsx \ --targetprofile:netcore \ --target:library \ -r:/root/.nuget/packages/fsharp.data/4.2.2/lib/netstandard2.0/FSharp.Data.dll \ --out:/repro/work/my-dll.dll # the below fails RUN ls /repro/work/my-dll.dll
Expected behavior
The work directory should not get deleted and my-dll.dll should be there.
work
my-dll.dll
Actual behavior
The work directory gets deleted and the compilation output is lost.
Known workarounds
Do not use rooted paths as the --out flag values.
Related information
Provide any related information (optional):
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
fsc
deletes the output directory when the--out
flag is set to a rooted path and the compiled script contains NuGet references.Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
The
work
directory should not get deleted andmy-dll.dll
should be there.Actual behavior
The
work
directory gets deleted and the compilation output is lost.Known workarounds
Do not use rooted paths as the
--out
flag values.Related information
Provide any related information (optional):
The text was updated successfully, but these errors were encountered: