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.VisualStudio.Sdk meta-package and clean up versions and package references #71111

Merged
merged 14 commits into from
Jan 18, 2024

Conversation

tmat
Copy link
Member

@tmat tmat commented Dec 5, 2023

For now, uses Microsoft.VisualStudio.Sdk 17.9.35796-preview.1 as Integration Test machines currently have 17.9 Preview 1.

Switch to Central Package Versioning.

Fixes source build.

Virtual Mono-repo build only reports a few warnings with this change:

/vmr/dotnet/src/roslyn/artifacts/sb/package-cache/system.collections.immutable/9.0.0-alpha.1.24061.26/buildTransitive/netcoreapp2.0/System.Collections.Immutable.targets(4,5): warning : System.Collections.Immutable 9.0.0-alpha.1.24061.26 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net9.0 or later. You may also set <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk. [/vmr/dotnet/src/roslyn/artifacts/sb/src/src/CodeStyle/Tools/CodeStyleConfigFileGenerator.csproj]
/vmr/dotnet/src/roslyn/artifacts/sb/package-cache/system.reflection.metadata/9.0.0-alpha.1.24061.26/buildTransitive/netcoreapp2.0/System.Reflection.Metadata.targets(4,5): warning : System.Reflection.Metadata 9.0.0-alpha.1.24061.26 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net9.0 or later. You may also set <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk. [/vmr/dotnet/src/roslyn/artifacts/sb/src/src/CodeStyle/Tools/CodeStyleConfigFileGenerator.csproj]
/vmr/dotnet/src/roslyn/artifacts/sb/package-cache/system.collections.immutable/9.0.0-alpha.1.24061.26/buildTransitive/netcoreapp2.0/System.Collections.Immutable.targets(4,5): warning : System.Collections.Immutable 9.0.0-alpha.1.24061.26 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net9.0 or later. You may also set <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk. [/vmr/dotnet/src/roslyn/artifacts/sb/src/src/CodeStyle/Tools/CodeStyleConfigFileGenerator.csproj]
/vmr/dotnet/src/roslyn/artifacts/sb/package-cache/system.reflection.metadata/9.0.0-alpha.1.24061.26/buildTransitive/netcoreapp2.0/System.Reflection.Metadata.targets(4,5): warning : System.Reflection.Metadata 9.0.0-alpha.1.24061.26 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net9.0 or later. You may also set <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk. [/vmr/dotnet/src/roslyn/artifacts/sb/src/src/CodeStyle/Tools/CodeStyleConfigFileGenerator.csproj]
        4 Warning(s)
        0 Error(s)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 5, 2023
@tmat tmat force-pushed the Dependencies branch 2 times, most recently from 4365383 to dbcbe8c Compare December 14, 2023 17:49
@tmat tmat changed the title Use Microsoft.VisualStudio.Sdk meta-package and clean up versions and… Use Microsoft.VisualStudio.Sdk meta-package and clean up versions and package references Dec 22, 2023
@tmat tmat marked this pull request as ready for review December 22, 2023 01:00
@tmat tmat requested review from a team as code owners December 22, 2023 01:00
@tmat
Copy link
Member Author

tmat commented Dec 22, 2023

@jasonmalinowski @sharwell @dotnet/roslyn-ide PTAL

Copy link
Member

@sharwell sharwell left a comment

Choose a reason for hiding this comment

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

Not quite sure how to verify this overall. Moving to Central Package Versioning seems essential for this to work out.

@tmat
Copy link
Member Author

tmat commented Dec 22, 2023

Not quite sure how to verify this overall. Moving to Central Package Versioning seems essential for this to work out.

Will follow up on that.

@tmat tmat requested a review from a team as a code owner January 4, 2024 22:08
@tmat tmat force-pushed the Dependencies branch 2 times, most recently from 4b30a93 to 6d86c9e Compare January 5, 2024 02:40
@genlu
Copy link
Member

genlu commented Jan 6, 2024

Switch to Central Package Versioning.

Does this mean we don't have to deal with the version conflicts between the transitive dependency of some package from multiple references anymore?

@tmat
Copy link
Member Author

tmat commented Jan 6, 2024

Does this mean we don't have to deal with the version conflicts between the transitive dependency of some package from multiple references anymore?

Yeah, we shouldn't be.

@jaredpar
Copy link
Member

jaredpar commented Jan 8, 2024

How does central package versioning help out with the conflicts? Or why did we want to include it in this change?

I'm not against the change but I wanted to understand a bit better the motivations for moving to it.

@jaredpar jaredpar self-assigned this Jan 16, 2024

public static ISymbol? GetAnySymbol(this SymbolInfo info)
=> info.Symbol ?? info.CandidateSymbols.FirstOrDefault();

public static ImmutableArray<ISymbol> GetBestOrAllSymbols(this SymbolInfo info)
{
if (info.Symbol != null)
return [info.Symbol];
return ImmutableArray.Create(info.Symbol);
Copy link
Member

Choose a reason for hiding this comment

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

Why did we need to undo collection expressions here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not 100% sure. Source build was failing.

Copy link
Member

Choose a reason for hiding this comment

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

The source build in CI or the full source build?

Copy link
Member Author

Choose a reason for hiding this comment

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

CI

@tmat
Copy link
Member Author

tmat commented Jan 17, 2024

@tmat FYI, something is wrong with the integration tests on this PR - its finishing in ~5minutes https://dev.azure.com/dnceng-public/public/_build/results?buildId=529108&view=results

Fixed.

@tmat tmat enabled auto-merge (squash) January 18, 2024 04:18
@tmat tmat merged commit db94f71 into dotnet:main Jan 18, 2024
31 checks passed
@ghost ghost added this to the Next milestone Jan 18, 2024
@tmat tmat deleted the Dependencies branch January 18, 2024 05:38
Copy link
Member

Choose a reason for hiding this comment

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

@tmat - probably this was an accident?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants