`CompileBefore`/`CompileAfter` is lost due to the `FSharpSourceCodeCompileOrder` target

[auduchinok]

Hi,

We use the knowledge about CompileBefore and CompileAfter extensively in Rider. With the newer SDKs this data is lost because of the new way these files are passed to compiler. Files that were initially added as CompileBefore are now added to Compile item collection instead. Even though the final file order is correct, the info about the original item type is lost, which introduces regressions in our case.

Could we preserve this knowledge as metadata in the rewritten Compile items, please?

[vzarytovskii]

#16771 was implemented in
#17103. <Compile> item has metadata about order:

[auduchinok]

@vzarytovskii This only seem to apply to the items having the metadata before moving groups in FSharpSourceCodeCompileOrder target. Items originally added to CompileBefore group don't have this metadata and are silently added to Compile, so they lose the knowledge about the original item type. It's easy to see on AssemblyInfo.fs file in console template.

[KevinRansom]

@auduchinok,
Hey, they weren't really supposed to be used for anything other than: Microsoft.FSharp.Targets build order. And the change to a metadata version was to address other SDK features that rely solely on compile order. I expect adding the metadata in the scenario it is currently lost is not that hard.