Tuomas Hietanen

Because most of the TPs still refer ProvidedTypes.fs as a paket-dependencies file, not as NuGet package, the DefineConstants can be defined in the project referring the file. > It adds...

> But it seems preprocessors are out. Would you accept preprocessors at fsproj-level? So that there would be ProvidedTypesOld.fs and ProvidedTypesNew.fs ? I think lot of F# 4 usage comes...

By accepting a dependency to System.Memory in .NET Standard 2.0 (only) we'd get access to `.AsSpan()` and `ReadOnlySpan` which could make parsing more efficient in at least .NET Standard 2.1...

There are a lot of nested types in this one. The time is spent on ProvidedTypes.fs on method `.Compile(isHostedExecution)` This takes 7 seconds wait: `// phase 2 - emit member...

Sound good suggestion. What should the user code look like?

Sounds good to me (except task instead of async).

The problem I have with the current individuals feature is that it potentially performs a large database query at design time, and if you use an offline schema, the schema...

The list of individuals are read from the concurrent dictionary at compile-time/design-time and maybe at the beginning of the program, but then the queries are not actually hitting the database...

This could help the CI failure: https://github.com/fsprojects/FAKE/pull/2783

Maybe the failure is this asking 6.0.100: https://github.com/fsprojects/FAKE/blob/master/integrationtests/core-reference-assemblies-net60101-rollforward/before/global.json ...as the CI reports it here: https://github.com/fsprojects/FAKE/actions/runs/10092902189/job/27907519123?pr=2780#step:8:9360 There are other too, e.g. here: https://github.com/fsprojects/FAKE/blob/master/integrationtests/core-reference-assemblies-net60101/before/global.json