Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for .NET Core Tooling Preview3+ projects
See original GitHub issueSupport for .NET Core Tooling Preview3+ projects
When building API documentation for a project that uses .NET Core Preview 3 or higher (csproj), the build fails, because (roslyn?) is unable to parse PackageReference tags
Functional impact
API documentation can not be built for projects that use .NET Core
Minimal repro steps
- Create a docFx project
- Add a metadata reference to a csproj file
Expected result
The build would succeed and API documentation would be built.
Actual result
During the ‘generating metadata’ phase of the build, a warning is thrown opening the project.
Warning: Error opening project <project>.csproj: The attribute "Version" in element <PackageReference> is unrecognized.. Ignored.
No API documentation is built.
Further technical details
N/A
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:44 (18 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The *.cs workaround does not seem to be working properly for me. It builds most of the docs, but misses some of the cross references that worked with the old setup. This is the last showstopper to being able to update all my repos to the new project format. Any ETA on when this will happen, especially now that 2017 is RTM and released?
Looks like Roslyn 2.0-rc4 has made it’s way on to the official NuGet feed, any progress on this?