Can the F# compiler service 10 run on the net8 runtime?

[goswinr]

I am hosting the F# compiler service inside a larger app on the net8 runtime.
Using F#8 this works fine.
But should I also be able to host F#10 compiler service on net8 ?
So I can use the latest features of F#?

Currently I get a System.MissingMethodException: Method not found: 'Void System.Diagnostics.ActivitySource..ctor(System.String)'.
Is this because the hosting app has already the net8 version of System.Diagnostics.DiagnosticSource loaded ?
see goswinr/Fesh.Rhino#24

[T-Gro]

The FSharp.Compiler.Service is a net standard project, it works both for any modern dotnet as well as for .NET Framework 472.
If you reference the ns20 version of it (and not e.g. a custom built net10 build of it), I do not see why it should not work.

Are you referencing it as a package or building from source?

The missing method might be caused by dependency resolution, those can clash if the used libraries went trough breaking changes.
(IMO it should use Diagnostics from a package, and that package must not be pruned away)

[goswinr]

Thanks, Tomas, yes I just load nuget packages, I actually had the same problem hosting in Revit ( also a net8 host). see goswinr/Fesh.Revit#18
for now, I ll stick with F# 8 until I have found a way to debug this. Not sure how to go about this.
I guess using IL-Repack will not work because the compiler service FSI does Reflection.Emit and assumes FSharp.Core to be present (and not IL inlined) ?
I also noted that the F# core and compiler service version umbers always need to be matching. That is OK, just didn't know.

[T-Gro]

Statically linked F# core into the compiler is not a supported scenario - it isn't fully impossible, but I think it was simply never tried out by anyone.

Since a lot of FSharp.Core is F#-inlined, the compiler often works on the "F# optimization data" level from the binary resources rather than IL level when basic functions are used.

I will check the issue - since the package is netstandard, it should work fine when it gets the right dependencies (and compiler has just a handful).