-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Produce Microsoft.AspNetCore.Authorization as a package #10684
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
Conversation
This is needed for Blazor (client-side)
Might want to check the steps here: https://github.com/aspnet/AspNetCore/blob/master/docs/ReferenceAssemblies.md. Note the section on adding a new project. |
@JunTaoLuo Thanks and... why aren't you asleep? 😄 |
Could also consult #10669 as a reference. |
I was in the process of running eng\generateprojectreferences and it produced nothing BTW |
Hehe, I sleep at odd hours. I'll do a more thorough check in the morning but have you tried running |
Yeah, I think I got it figured out. |
/Azure-pipelines run |
1 similar comment
/Azure-pipelines run |
/Azure-pipelines run |
@aspnet/build I am not able to get this PR to run the required checks |
It's not only your PR and it's not only this repo e.g. https://github.com/aspnet/EntityFrameworkCore/pull/15878/checks?check_run_id=139437341. It appears to be GitHub flakiness but I'm not sure. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Hmm I expect eng/ProjectReferences.props to be updated after you run ./eng/scripts/GenerateProjectList.ps1 but I don't see that in the list of files changed. |
I ran both, but I'm gonna give it another try |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
/azp run |
Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see, we're just making them as shiping now. Makes sense.
This is required for client-side blazor, as Microsoft.AspNetCore.Components references is a package in the Blazor client-side case.