Closed
Description
Support 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
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
superyyrrzz commentedon Feb 14, 2017
Yes, Roslyn should be updated to support it. Currently we are waiting for its official release.
superyyrrzz commentedon Feb 15, 2017
Seems Roslyn 2.0-rc4 can open new csproj, but fail to extract info from it.
cpx86 commentedon Feb 20, 2017
Is there any work being done on this? VS2017 is just around the corner, and for libraries targeting the latest dotnet version, not being able to use DocFx is a bit of a problem.
DustinKingen commentedon Feb 25, 2017
I encountered this today too. I'm using .NET Core SDK 1.0 rc4 build 004771.
I created a new project:
Added docfx:
Add nuget reference to
docfx.console
indocs.csproj
.Added
src
node to thedocfx.json
.Add a C# class
src/App/Foo.cs
:Build App:
Build docfx:
Add xmlns to
App.csproj
Rebuild App
Rebuild docs
That's as far as I've gotten.
foxbot commentedon Mar 5, 2017
Looks like Roslyn 2.0-rc4 has made it's way on to the official NuGet feed, any progress on this?
sethjuarez commentedon Mar 8, 2017
Any word on a fix for this?
rschili commentedon Mar 8, 2017
As a workaround I'm including *.cs files directly now, that seems to work at least to some extent. Would love to see real support for the new .csproj files. The stable tooling has been released yesterday.
superyyrrzz commentedon Mar 9, 2017
I have still no success in parsing csproj using Roslyn 4.0-rc4. As @rschili mentioned above, including *.cs is a workaround for now. We are waiting for the stable version of Roslyn.
fubar-coder commentedon Mar 10, 2017
Why would anyone still use RC4 when RTM is available? BTW: RC4 is nearly a month old now (even the version on nuget.org).
EDIT: According to dotnet/roslyn#17439, the new multi-TFM MSBuild workspaces still aren't supported yet. So I guess that we have to wait for the next version.
cpx86 commentedon Mar 10, 2017
@fubar-coder The issue is that DocFx has been broken for MSBuild 2017 projects ever since they were introduced in RC3 and replaced project.json, and is still broken despite 2017 now being available as RTM.
ThadHouse commentedon Mar 14, 2017
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?
59 remaining items