-
Notifications
You must be signed in to change notification settings - Fork 868
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
Hard-to-diagnose "No metadata is generated" #1686
Comments
|
Is there anything else we can try rather than just install MS Build Tools 2015? I have multiple systems that have both 2015 and 2017 installed, and still can't generate metadata. I don't think that is the only dependency, or maybe something in VS 2017 is overriding something in the GAC causing docfx to fail. |
@ThadHouse in my case I was targeting multiple target frameworks. In case you have the same, you need to specify them in your docfx.json as described here: #1254 (comment) |
I'll double check that, but I think I've tried that before. I'm getting the error where no files are being returned by the MSBuildProject. But I'll try again. I might just end up putting a project.json back in my projects, because that does seem to actually work. |
What do you have instead? I think I've read something about xproj not being supported. But not sure :) |
I'm using new VS 2017 csproj files, which have never worked for me in docfx, even though theyre supposed to. |
Yes, for me that works. Public types/members? Maybe you can reference the project here? |
Yeah I've tried a ton of different things. Even example projects posted by both the docfx team, and other people that have posted issues don't work for me. Nothing related to the new csproj works for me. |
I was able to get it working on one of my machines (I don't know how...) However, AppVeyor still does not work for me, so something still is not right with the dependencies that are thought to be required. |
Hi @ThadHouse , is it possible for you to share your project & AppVeyor settings for me to take a look? |
https://github.com/robotdotnet/WPILib-Docs/tree/metadatatest Here's my repo that I have to generate the docs. The runBuild.ps1 script downloads the latest version of docfx, clone my repos, and then attempt to run docfx. The appveyor settings are in appveyor.yml. https://github.com/robotdotnet/FRC-Utilities This is probably my easy repo to test metadata generation if you want to try manually, since there isn't a lot in the repo, and only 2 targetplatforms. |
https://ci.appveyor.com/project/robotdotnet/wpilib-docs/build/master-35-qxdglprl Here's also the latest build attempt on AppVeyor |
Hi @ThadHouse According to https://github.com/robotdotnet/FRC-Utilities you are targeting multiple frameworks, could you add "properties": {
"TargetFramework": <one_of_your_framework>
} to your metadata section? |
MSBuildWorkspace.OpenSolutionAsync() and MSBuildWorkspace.OpenProjectAsync() do not give any notification that loading a solution or project failed. However, there is a WorkspaceFailed event that we can use to be notified when there is a problem. This logs the diagnotic information from this event to help the user troubleshoot. Related: * dotnet/roslyn#19978 (comment) * dotnet#1686 * dotnet#1708 (comment)
MSBuildWorkspace.OpenSolutionAsync() and MSBuildWorkspace.OpenProjectAsync() do not give any notification that loading a solution or project failed. However, there is a WorkspaceFailed event that we can use to be notified when there is a problem. This logs the diagnotic information from this event to help the user troubleshoot. Related: * dotnet/roslyn#19978 (comment) * #1686 * #1708 (comment)
Neither the TargetFramework nor the updated build tools requirement help this build on appveyor. Also tested the new logger function, and all it says is "Failed to parse file", so its not very helpful. |
MSBuildWorkspace.OpenSolutionAsync() and MSBuildWorkspace.OpenProjectAsync() do not give any notification that loading a solution or project failed. However, there is a WorkspaceFailed event that we can use to be notified when there is a problem. This logs the diagnotic information from this event to help the user troubleshoot. Related: * dotnet/roslyn#19978 (comment) * #1686 * #1708 (comment)
In relation to #165.
Even though I have
--logLevel Verbose
I cannot tell why the project is being skipped withWarning:No metadata is generated for XXX.
.The text was updated successfully, but these errors were encountered: