Steve Gilham

@Numpsy Of course it wouldn't - the published net6.0 fake-cli cannot ever work in the net8.0 environment - inability to work in later dotnet versions has been a known problem...

Doing a bit of archaeology to see what went on in the transition to net6.0, I noticed an interesting aspiration in the [relevant pull request](https://github.com/fsprojects/FAKE/pull/2609) - > The benefits of...

1) As noted above, referencing an earlier FSharp.Core e.g. by `dotnet add package FsharpCore -v 4.1.8` fails 2) As noted above, even after editing the project file manually to add...

The profusion of quite interesting error messages did suggest neglect/not-tested rather than a hard and explicit end-of-support (e.g. by emitting something like NETSDK1138, only as a build error, not a...

That would be super! As background -- the one particular assembly affected is the coverage recorder for [AltCover](https://github.com/SteveGilham/altcover), which is, yes, a codebase that's now over 10 years old, and...

Interesting difference in behaviour with .net sdk 6.0.100 -- using `dotnet new console -lang f# -o n2` and editing n2.fsproj to be like ``` Exe net20 all runtime; build; native;...

The `AltCover.Main.I.imageLoadResilient` call through which this filters is a pass that is already implicitly doing an `--ignoreExceptions` for likely malformed or mismatched symbol files; this appears to be a novel...

A fix is prepared and will appear in the next release.

Fixed in release v9.0.102

In principle, pretty much anything is possible, dependent on how much decompilation is worth doing. I presume that you want to have behaviour like ```C# if (condition) { throw new...