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

[Prev6] Update MicrosoftPrivateIntellisensePackage and XmlDocFileRoot #38118

Conversation

carlossanlop
Copy link
Member

@carlossanlop carlossanlop commented Jun 18, 2020

PR for master: #38109

This PR will update the Intellisense from Preview6 with what was generated from Preview5.

XmlDocFileRoot was defined in two places: packaging.props and docs.targets.
Moved it to a higher level to ensure it's only defined once, in Directory.Build.props. Made sure to define it after NuGetPackageRoot is defined.
Also made sure the folder it reads is net instead of netcoreapp, because the Docs build saves the .NET 5.0 intellisense files in the net folder, and the .NET 3.1 intellisense files in the netcoreapp folder.
Updated the nupkg to consume to the latest available version in the feed 20200602.3, which contains the Preview5 APIs.

Note: The version is not being downgraded from 3.1 to 3.0. The Docs build uploads the nupkg to the feed with that name. We will ask them to rename it to avoid confusion.

@ghost
Copy link

ghost commented Jun 18, 2020

Tagging subscribers to this area: @ViktorHofer
Notify danmosemsft if you want to be subscribed.

@carlossanlop
Copy link
Member Author

carlossanlop commented Jun 18, 2020

The CI will most likely hit a build failure. Santi and I are investigating it.

Update: Fixed. Moved the XmlDocFileRoot definition to Versions.props.

@safern
Copy link
Member

safern commented Jun 18, 2020

@danmosemsft @mmitche can we take this change for Preview6 still? Currently the intellisense we're shipping are from 3.1.

@mmitche
Copy link
Member

mmitche commented Jun 18, 2020

@danmosemsft @mmitche can we take this change for Preview6 still? Currently the intellisense we're shipping are from 3.1.

We don't have the runway for 5.0 p6

@safern
Copy link
Member

safern commented Jun 18, 2020

We don't have the runway for 3.1

What do you mean? I meant that the intellisense xml files that we're including in Preview6 and master without this change are using the xml files from 3.1 release, so it would be nice if we could take this change to use the xml files produced from 5.0-Preview6.

@danmoseley
Copy link
Member

Can you clarify the impact -- you're saying that currently if I use VS to develop against Preview 6 (and previous 5.0 previews) I will get no intellisense for API that's new in 5.0? Or I just won't get the descriptions?

@mmitche
Copy link
Member

mmitche commented Jun 18, 2020

We don't have the runway for 3.1

What do you mean? I meant that the intellisense xml files that we're including in Preview6 and master without this change are using the xml files from 3.1 release, so it would be nice if we could take this change to use the xml files produced from 5.0-Preview6.

Sorry I meant p6

@safern
Copy link
Member

safern commented Jun 18, 2020

Or I just won't get the descriptions?

Just the descriptions. This has been this way for all the previous previews, so we could wait for P7.

@carlossanlop
Copy link
Member Author

@safern the build failed here, even though the changes are the same as in master.

@mmitche should we close this PR then?

@mmitche
Copy link
Member

mmitche commented Jun 18, 2020

@safern the build failed here, even though the changes are the same as in master.

@mmitche should we close this PR then?

Yep

@safern safern closed this Jun 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
@carlossanlop carlossanlop deleted the intellisensePrev5 branch February 7, 2024 06:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants