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

Use Microsoft.AspNetCore.Razor.Language for all CPDs #18669

Closed
wants to merge 1 commit into from

Conversation

wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Jan 29, 2020

Use Microsoft.AspNetCore.Razor.Language for all CoherentParentDependencies, except for the dependency on Roslyn (which isn't depended on by AspNetCore-Tooling). This will allow us to avoid DARC choosing EFCore as the parent for any CPDs, which would cause us to downgrade to 3.1 versions of corefx (now runtime) dependencies.

@mmitche @dougbu @JunTaoLuo PTAL

@wtgodbe wtgodbe requested a review from dougbu as a code owner January 29, 2020 21:20
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jan 29, 2020
Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look bizarre. Why is the CPD hierarchy going to be so messy?

I could understand changing CoherentParentDependency="Microsoft.NETCore.App.Runtime.win-x64" to CoherentParentDependency="Microsoft.Extensions.Logging" i.e. use the logging package for all dotnet/runtime dependencies. But, do not take dotnet/extensions out of the hierarchy until that repo is consolidated.

I also suggest changing CPD in dotnet/extensions and dotnet/aspnetcore-tooling before doing anything in this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants