Skip to content
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

DocComment XML not shipping in Microsoft.NETCore.App.Ref 9.0.100-rc1 #106825

Closed
JoeRobich opened this issue Aug 22, 2024 · 5 comments · Fixed by #107334
Closed

DocComment XML not shipping in Microsoft.NETCore.App.Ref 9.0.100-rc1 #106825

JoeRobich opened this issue Aug 22, 2024 · 5 comments · Fixed by #107334
Assignees
Labels
area-Infrastructure-libraries blocking-release in-pr There is an active PR which will close this issue when it is merged
Milestone

Comments

@JoeRobich
Copy link
Member

This breaks hover support in the VSCode C# extension.

Expected
to see .XML files for each of the libraries like we shipped with 9.0.0-preview.7.

Image

Actual
see no .XML files.

Image

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Aug 22, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Aug 22, 2024
@vcsjones vcsjones added area-Infrastructure-libraries and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Aug 22, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

@carlossanlop
Copy link
Member

Thanks for reporting. We're aware of this. We just got that fixed with #106179

The fix will go into RC1.

Note that there are also many docs that we haven't updated yet, which will get start showing up on RC2.

@carlossanlop carlossanlop removed the untriaged New issue has not been triaged by the area owner label Aug 22, 2024
@ericstj
Copy link
Member

ericstj commented Aug 26, 2024

@carlossanlop I spot checked https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet9/NuGet/Microsoft.NETCore.App.Ref/overview/9.0.0-rc.1.24421.1
And https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet9/NuGet/Microsoft.NETCore.App.Ref/overview/9.0.0-rc.2.24423.10

DOC XML is still missing. Can you double check that there's not something else broken here?

@ericstj
Copy link
Member

ericstj commented Sep 3, 2024

I had a look:

<DocFilesToPackage Include="$(MicrosoftNetCoreAppRefPackRefDir)%(LibrariesRefAssemblies.FileName).xml" Condition="Exists('$(MicrosoftNetCoreAppRefPackRefDir)%(LibrariesRefAssemblies.FileName).xml')"/>

Is trying to grab the files from MicrosoftNetCoreAppRefPackRefDir which is artifacts\bin\microsoft.netcore.app.ref\ref\net9.0

Inspecting this folder the problems files exist with the name System.*.intellisense-package.xml instead of System.*.xml. This was caused by 9477e94. I'll see if I can make a fix.

@ericstj
Copy link
Member

ericstj commented Sep 4, 2024

Yeah, that change regressed it. I think that was a bad change as the build process doesn't actually rename the file when copying:
https://github.com/dotnet/msbuild/blob/7cf66090a764f0f239671e4877255efe7ba91155/src/Tasks/Microsoft.Common.CurrentVersion.targets#L398
https://github.com/dotnet/msbuild/blob/7cf66090a764f0f239671e4877255efe7ba91155/src/Tasks/Microsoft.Common.CurrentVersion.targets#L4942-L4944
The only reason it's not broken in the output directory is because the FinalDocFile gets set before we redefine DocFileItem.

The phase that copies to the shared framework gets the renamed items and doesn't ever give them the correct name.

<DocumentationFileToCopy Include="@(SharedFrameworkAssembly->WithMetadataValue('IsPrivateAssembly', 'false')->Metadata('DocFileItem'))" />
</ItemGroup>
<Copy SourceFiles="@(DocumentationFileToCopy)"

The simpler fix here is to use a sub-directory for the touched file instead of a different filename. #107334 does this.

@dotnet-policy-service dotnet-policy-service bot added the in-pr There is an active PR which will close this issue when it is merged label Sep 4, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-libraries blocking-release in-pr There is an active PR which will close this issue when it is merged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants