Steve Gilham

I'm afraid I don't have a repro case; all the information I have is a stack trace from [an issue against my AltCover project](https://github.com/SteveGilham/altcover/issues/135), which was enough to let me...

The simple example provided is using the `DefaultAssemblyResolver` type -- it just reads and then immediately writes a sample assembly; and its behaviour changes depending on the target platform to...

>Cecil cannot do this for you. That's why I'm making this issue report. It could and should avoid such platform-inconsistent behaviour, and can do it simply by changing the compile-time...

[PR #864](https://github.com/jbevain/cecil/pull/864) does the core of the work, sufficient to let one write an assembly resolver that sub-classes e.g. `DefaultAssemblyResolver` and re-uses the existing tested search implementations and can say...

You can get the attribute type name and examine the associated binary blob data w/o any resolver as the following example demonstrates ```csharp using System; using System.IO; using System.Linq; using...

I'd have to learn my way around the codebase -- I've not peered under the hood here before.

[The file from which this example was extracted](https://github.com/SteveGilham/altcover/commit/82098d9a15177d7d078ace896d8f21386c3eab51#diff-b8eb3ac4a6f8cd76e40bb7ddd4dbfe52d96c0b05d573b266ae27e1c3c6da074e) now simply yields ``` Processing .\AltCover.Tests\Tests2.fs Formatting .\AltCover.Tests\Tests2.fs lead to invalid F# code ``` with no further hint as to what was...

Having used `--force`, I see the issue still recurring with fantomas 5.0.0; presumably this is what was detected as invalid code. So far, alas, I have not been able to...

Note: fantomas 5.0.2 has resolved the original issue -- presumably why I was unable to produce a repro using the online tool. The [related issue in the comment above](https://github.com/fsprojects/fantomas/issues/2110#issuecomment-1254819388) still...

New issue #2529 created.