-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSharp library not used for generating API docs #857
Comments
Hi there, does it get picked up when you specify it explicitly via The help text says |
Does this have to be set explicitly? I do not set anything in that regard on the F# projects. i am publishing all libraries (including the C# library) as nuget packages via
I have not tried it now, but remember it not working when i tried last time. Will try it again later and report back
How are multiple projects expected to be passed here? comma-separated full paths? one directory containing all projects? |
Hmm, I'm not quite sure, you could try:
I don't think it will be
Yeah, definitely try full paths when relative ones don't work.
No, it does expect actual projects, not directories. |
So this is really weird. If i run this fake build task: let watchDocs =
BuildTask.create "WatchDocs" [ build ] {
printfn "watching docs with stable version %s" stableDocsVersionTag
runDotNet
"fsdocs watch --eval --clean --properties Configuration=Release --projects <absolute project paths here>
"./"
} which basically only runs dotnet fsdocs watch --eval --clean --properties Configuration=Release --projects <absolute project paths here> i get this error (for ALL, F# and C#) projects:
if i run the same command from the command line, everything works out. |
Euhm, yeah this is some fun stuff. Project cracking fails and who knows what FAKE is doing to influence it. |
Win 11 Pro Version 10.0.22621 Build 22621 But it seems like the workaround of just building with fake and then calling the tool manually with |
If you were running with the dotnet 8 preview SDK I had some environment variables in mind you could give a try. But as you are sticking to the stable 6 SDK I have no immediate idea what you could try. I would work around it for now. But we should keep this ticket open and provide a better DX when project cracking fails. |
At some point the fsdocs tool stopped generating API docs for a C# library (
Plotly.NET.CSharp
) in a mixed F#/C# solution (https://github.com/plotly/Plotly.NET/tree/dev/src). I am 100% certain that this worked in the past. Now the tool only selects the F# projects for API doc generation:I have a build step that builds all projects including the C# project before starting docs generation, so the binaries are there.
Could it be a problem that the C# project targets .net6.0 ?
The text was updated successfully, but these errors were encountered: