FS0243 - Unrecognized option: '--realsig-'

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:I'm unable to use this version] [regression]
I upgraded from VS 2022 17.10.4 to 17.11.0 and now when I build my solution (either in the IDE or via build agent VSBuild task), the build fails with the following error:
Severity Code Description Project File Line Suppression State
Error (active) FS0243 Unrecognized option: '--realsig-' Semaphore.Accelerus.Fs.UI.Core C:\Development\Accelerus\Accelerus\Semaphore.Accelerus.Fs.UI.Core\FSC 1

There are 4 F# / Fable projects in the solution and all 4 report the same error.

---

Original Comments

Feedback Bot on 8/14/2024, 09:31 AM:

(private comment, text removed)

---

Original Solutions

(no solutions)

[vzarytovskii]

Same as
https://developercommunity.visualstudio.com/t/F-projects-fail-to-build/10722863?sort=newest&topics=visual+studio+2019&WT.mc_id=WD-MVP-5003763

[vzarytovskii]

Turns out it's a bug when options are passed anyway to the underlying compiler, even if it doesn't support it (17.11 passes realsig- and 17.12 will pass realsig+). Fix would be to not pass the "default" one, and rely on compiler taking care of it.
We should backport the fix to 17.11.

[baronfel]

I was looking at this too, and I think it's maybe a bit more fundamental - FSharp in VS loads targets from VS but the compiler from the SDK. Those shouldn't ever be mismatched like that - we should keep targets + compiler in alignment for compatibility/understandability purposes. I was talking to @jaredpar and @rainersigwald earlier today and this split confused all of us. Roslyn allows choosing which one you want by way of a package that sets certain properties to load targets and compiler references, perhaps that could be a way forward?

[vzarytovskii]

and this split confused all of us

Are you referring to this issue or something else?