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

Add Microsoft.CodeAnalysis/4.9 dependencies #870

Merged
merged 18 commits into from
Jan 22, 2024

Conversation

ViktorHofer
Copy link
Member

... necessary to consume new Roslyn dependencies. Roslyn recently updated to 8.0.0 dependencies which makes this change necessary.

Unblocks dotnet/runtime#97152

... necessary to consume new Roslyn dependencies. Roslyn recently updated
to 8.0.0 dependencies which makes this change necessary.

Unblocks dotnet/runtime#97152
@ViktorHofer
Copy link
Member Author

ViktorHofer commented Jan 22, 2024

@mthalman
Copy link
Member

How is this intended to resolve dotnet/runtime#97152? Those changes aren't even trying to use 4.10.0.

@ViktorHofer ViktorHofer changed the title Add Microsoft.CodeAnalysis/4.10 dependencies Add Microsoft.CodeAnalysis/4.9 dependencies Jan 22, 2024
@ViktorHofer
Copy link
Member Author

ViktorHofer commented Jan 22, 2024

How is this intended to resolve dotnet/runtime#97152? Those changes aren't even trying to use 4.10.0.

Fixed the title. It's roslyn4.9 that brings the 8.0.0 packages in. Remember, you helped with that investigation.

eng/Build.props Outdated
Comment on lines 30 to 37
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Composition.TypedParts.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Composition.Runtime.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Composition.Hosting.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Composition.Convention.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Composition.AttributedModel.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.IO.Pipelines.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Text.Encoding.CodePages.8.0.0.csproj" />
<DependencyPackageProjects Include="$(RepoRoot)src\referencePackages\src\**\System.Threading.Channels.8.0.0.csproj" />
Copy link
Member

Choose a reason for hiding this comment

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

These need to be sorted in dependency order. For example, I see that System.Composition.TypedParts depends on System.Composition.Hosting.

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought I added them in sorted order. If the order is wrong, shouldn't I get a build or prebuilt error?

Copy link
Member

@MichaelSimons MichaelSimons Jan 22, 2024

Choose a reason for hiding this comment

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

It is documented in the readme

Add DependencyPackageProjects for all new projects in the eng/Build.props in the correct dependency order.

Unfortunately you won't get a build error or prebuilts reported. This is why we need to get project to project references defined so that these DependencyPackageProjects can be removed.

Copy link
Member Author

Choose a reason for hiding this comment

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

Right, I followed those instructions but looks like I got something in the order wrong. Without build validation or someone telling me that the order is wrong, I would have never noticed that.

@ViktorHofer ViktorHofer enabled auto-merge (squash) January 22, 2024 15:51
@ViktorHofer ViktorHofer merged commit 1b84747 into main Jan 22, 2024
4 checks passed
@ViktorHofer ViktorHofer deleted the AddCodeAnalysis410Dependencies branch January 22, 2024 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants