Replies: 4 comments
-
If you need to invoke FSC.dll directly (or use compiler service), it needs all references passed to it in order to work properly, we don't do any discovery inside (only when using msbuild and fsi). |
Beta Was this translation helpful? Give feedback.
-
When invoking the compiler explicitly like this, you need to provide all the DLLs to compile against. This is normally something that MSBuild does for you as part of dotnet build, but you take that responsibility on yourself when using the APIs. |
Beta Was this translation helpful? Give feedback.
-
I will attempt tomorrow. Also as an aside, I don't understand why I would need any of those dlls anyway. I'm deffo not doing any winforms or web services in my script. Sigh, dotnet. |
Beta Was this translation helpful? Give feedback.
-
Installing .net framework 4.7.2 magically fixed it. How does this impact deployment? If I want to host the fsc compiler in, say, a game - do I need to distribute .net framework 4.7.2 runtime? Will this approach work on Linux? Related issue: |
Beta Was this translation helpful? Give feedback.
-
Compiler does not work from either inside F# project or running fsc directly.
Inside F# project:
CLI:
Repro steps
Provide the steps required to reproduce the problem:
<PackageReference Include="FSharp.Compiler.Service" Version="43.7.300" />
FSharp.Compiler.CodeAnalysis
,FSharpChecker
,checker.Compile
.Fails with errors about the four missing dlls screengrabbed.
Expected behavior
It compiles the dll.
Actual behavior
It doesn't compile the dll.
Known workarounds
No idea.
Related information
Hardware, OS etc described in repro steps.
Beta Was this translation helpful? Give feedback.
All reactions