Florian Verdonck

@baronfel turns out you can put the `props` file in the [buildTransitive](https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets) and that way if will be evaluated for `A` as well. Works like a charm 🪄

> If I understand correctly, it means that the user needs to write Yes, although we can drop the `ExcludeAssets` and filter that out programmatically in `ProjectCracker`. That wouldn't be...

> is what does the compile refers to here? See https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets, "Contents of the lib folder and controls whether your project can compile against the assemblies within the folder" >...

You may need to have `Plugin` in your assembly name for the filtering to kick in. I did some experiment with a plugin a while ago and I had `--exclude...

Nah, that might not be it. Do you have ```fsharp // Tell Fable to scan for plugins in this assembly [] do () ``` in your plugin assembly as well?

Only `` needs to be `net6.0`. You can still use a higher SDK. I'm guessing it needs to be `net6.0`, because the Fable CLI tool is on that version: https://github.com/fable-compiler/Fable/blob/308aceff8602cfb0f6242c7fa2e85acd29413506/src/Fable.Cli/Fable.Cli.fsproj#L6

@MangelMaxime where in https://github.com/fable-compiler/fable-compiler.github.io/tree/dev/docs/docs would be a good place to write some docs on what we learned in this thread?

Project cracking would still need to be solved for the Vite plugin. However, there are situations where you want to go with a hardcoded or custom project. I'm thinking about...

Oh, that is interesting. On the topic of project cracking, in dotnet 8 RC 2 you can do the following: ``` dotnet msbuild /t:ResolveAssemblyReferencesDesignTime,ResolveProjectReferencesDesignTime,ResolvePackageDependenciesDesignTime,FindReferenceAssembliesForReferences,_GenerateCompileDependencyCache,_ComputeNonExistentFileProperty,BeforeBuild,BeforeCompile,CoreCompile /p:DesignTimeBuild=True /p:SkipCompilerExecution=True /p:ProvideCommandLineArgs=True --getItem:FscCommandLineArgs ``` This...

> This could remove the trick we do with creating a .csproj for having BuildAnalyzer to work correctly. I agree this was probably more robust than `proj-info`, but in my...