Skip to content

Fix entries in Version.Details.xml and make version overriding clearer#11561

Merged
rainersigwald merged 2 commits intomainfrom
fix-version-details-xml
Mar 10, 2025
Merged

Fix entries in Version.Details.xml and make version overriding clearer#11561
rainersigwald merged 2 commits intomainfrom
fix-version-details-xml

Conversation

@akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Mar 10, 2025

Follow-up to #11145.

We were missing the entry for System.Text.Encoding.CodePages and the source-build-externals intermediate for vs-solutionpersistence in Version.Details.xml which caused a prebuild in dotnet/sdk#47377 and version mismatches in dotnet/sdk#47376.

Also simplified the way we reference the different package versions a bit to make it clearer and synced the list of packages between Version.Details.xml/Versions.props/Packages.props.

Depends on #11555

Follow-up to #11145. We were missing the entry for System.Text.Encoding.CodePages in Version.Details.xml which caused a prebuild in dotnet/sdk#47377.

Also simplified the way we reference the different package versions a bit to make it clearer.
…builtBaseline.xml

We now properly reference it from source-build-externals
@akoeplinger akoeplinger force-pushed the fix-version-details-xml branch from 51274a8 to c7f1f7a Compare March 10, 2025 19:06
@rainersigwald rainersigwald enabled auto-merge (squash) March 10, 2025 19:08
@rainersigwald rainersigwald merged commit 64ea5d7 into main Mar 10, 2025
10 checks passed
@rainersigwald rainersigwald deleted the fix-version-details-xml branch March 10, 2025 21:40
@ViktorHofer
Copy link
Member

/backport to vs17.14

@github-actions
Copy link
Contributor

Started backporting to vs17.14: https://github.com/dotnet/msbuild/actions/runs/13784257663

@github-actions
Copy link
Contributor

@ViktorHofer backporting to "vs17.14" failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Fix entries in Version.Details.xml and make version overriding clearer
Using index info to reconstruct a base tree...
M	eng/Packages.props
M	eng/Versions.props
M	eng/dependabot/Packages.props
Falling back to patching base and 3-way merge...
Auto-merging eng/dependabot/Packages.props
CONFLICT (content): Merge conflict in eng/dependabot/Packages.props
Auto-merging eng/Versions.props
CONFLICT (content): Merge conflict in eng/Versions.props
Auto-merging eng/Packages.props
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Fix entries in Version.Details.xml and make version overriding clearer
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@ViktorHofer
Copy link
Member

Needs #11571 merged first.

ViktorHofer pushed a commit that referenced this pull request Mar 11, 2025
#11561)

Follow-up to #11145. We were missing the entry for System.Text.Encoding.CodePages in Version.Details.xml which caused a prebuild in dotnet/sdk#47377.

Also simplified the way we reference the different package versions a bit to make it clearer.

Remove Microsoft.VisualStudio.SolutionPersistence from SourceBuildPrebuiltBaseline.xml, since we now properly reference it from source-build-externals
ViktorHofer added a commit that referenced this pull request Mar 11, 2025
…ries in Version.Details.xml (#11571)

* Remove deprecated 4.3.* package references

Both "System.Runtime" and "System.Private.Uri" are inbox in .NETCoreApp since ~2017 and don't need to be referenced explicitly anymore.

They were referenced here as external dependencies brought vulnerable netstandard1.x dependencies in which were then flagged by CG.

That isn't the case anymore. xunit, shouldly and other packages with their corresponding versions used in this repo don't bring netstandard1.x in anymore.

Don't reference "System.Net.Http" for the same reason. It is inbox on .NET Framework, .NETCoreApp and .NET Standard. On .NET Framework a "<Reference Include="System.Net.Http" />" item is needed as it isn't part of the default referenced assemblies.

Note that this change will help when starting to consume a .NET 10 SDK as those would get flagged by NuGet Prune Package Reference and NuGet Audit.

* Avoid netstandard1.x dependencies

* fix build

* Fix entries in Version.Details.xml and make version overriding clearer (#11561)

Follow-up to #11145. We were missing the entry for System.Text.Encoding.CodePages in Version.Details.xml which caused a prebuild in dotnet/sdk#47377.

Also simplified the way we reference the different package versions a bit to make it clearer.

Remove Microsoft.VisualStudio.SolutionPersistence from SourceBuildPrebuiltBaseline.xml, since we now properly reference it from source-build-externals

---------

Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
maridematte added a commit that referenced this pull request Mar 19, 2025
* Localized file check-in by OneLocBuild Task: Build definition ID 9434: Build ID 11081403

* Update Versions.props VersionPrefix

* Update Versions.props VersionPrefix

* [vs17.14] Remove deprecated 4.3.* System package references & fix entries in Version.Details.xml (#11571)

* Remove deprecated 4.3.* package references

Both "System.Runtime" and "System.Private.Uri" are inbox in .NETCoreApp since ~2017 and don't need to be referenced explicitly anymore.

They were referenced here as external dependencies brought vulnerable netstandard1.x dependencies in which were then flagged by CG.

That isn't the case anymore. xunit, shouldly and other packages with their corresponding versions used in this repo don't bring netstandard1.x in anymore.

Don't reference "System.Net.Http" for the same reason. It is inbox on .NET Framework, .NETCoreApp and .NET Standard. On .NET Framework a "<Reference Include="System.Net.Http" />" item is needed as it isn't part of the default referenced assemblies.

Note that this change will help when starting to consume a .NET 10 SDK as those would get flagged by NuGet Prune Package Reference and NuGet Audit.

* Avoid netstandard1.x dependencies

* fix build

* Fix entries in Version.Details.xml and make version overriding clearer (#11561)

Follow-up to #11145. We were missing the entry for System.Text.Encoding.CodePages in Version.Details.xml which caused a prebuild in dotnet/sdk#47377.

Also simplified the way we reference the different package versions a bit to make it clearer.

Remove Microsoft.VisualStudio.SolutionPersistence from SourceBuildPrebuiltBaseline.xml, since we now properly reference it from source-build-externals

---------

Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>

* Don't ngen StringTools.net35 (#11544)

This assembly shouldn't ever be loaded in the net4x context so don't spend the install time ngening it.

* Make SolutionParser package reference private  (#11603)

Context
The VS insertion is currently failing due to the SolutionParser version being upgraded beyond the version used by VS. Made the change so this reference is not exposed and so the insertions do not fail.

---------

Co-authored-by: dotnet bot <dotnet-bot@dotnetfoundation.org>
Co-authored-by: Jenny Bai <v-jennybai@microsoft.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Co-authored-by: Rainer Sigwald <raines@microsoft.com>
Co-authored-by: Mariana Dematte <magarces@microsoft.com>
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