Skip to content

Don't ngen StringTools.net35#11544

Merged
rainersigwald merged 1 commit intovs17.14from
exp/no-net35-ngen
Mar 11, 2025
Merged

Don't ngen StringTools.net35#11544
rainersigwald merged 1 commit intovs17.14from
exp/no-net35-ngen

Conversation

@rainersigwald
Copy link
Copy Markdown
Member

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

This assembly shouldn't ever be loaded in the net4x context so don't spend the install time ngening it.
@rainersigwald rainersigwald added the Area: Visual Studio Issues related to interactions with Visual Studio or project systems. label Mar 5, 2025
@rainersigwald rainersigwald requested a review from SimaTian March 5, 2025 15:32
@rainersigwald rainersigwald self-assigned this Mar 5, 2025
@dotnet-policy-service
Copy link
Copy Markdown
Contributor

Hello @rainersigwald, I noticed that you’re changing an .swr file or any file under src/Package/MSBuild.VSSetup.. Please make sure to validate this change by an experimental VS insertion. This is accomplished by pushing to an exp/* branch, which requires write permissions to this repo.

@rainersigwald
Copy link
Copy Markdown
Member Author

Exp insertion passed perf DDRITs: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullRequest/616357#1741610257.

@rainersigwald rainersigwald marked this pull request as ready for review March 10, 2025 20:05
@SimaTian
Copy link
Copy Markdown
Member

Exp insertion passed perf DDRITs: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullRequest/616357#1741610257.

Is there a way to quickly check if it improved any of the 8 regressions we care about? (I just checked one of them manually - it didn't regress further but it didn't improve it either)

@JanProvaznik
Copy link
Copy Markdown
Member

do we want this in 17.14?

@rainersigwald
Copy link
Copy Markdown
Member Author

@SimaTian not "quickly" that I know of, manual per-scenario-per-metric check is all I know too.

@rainersigwald
Copy link
Copy Markdown
Member Author

do we want this in 17.14?

Yeah probably.

@rainersigwald rainersigwald changed the base branch from main to vs17.14 March 11, 2025 14:20
@rainersigwald rainersigwald enabled auto-merge (squash) March 11, 2025 14:20
@rainersigwald rainersigwald merged commit b1383be into vs17.14 Mar 11, 2025
@rainersigwald rainersigwald deleted the exp/no-net35-ngen branch March 11, 2025 15:10
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

Area: Visual Studio Issues related to interactions with Visual Studio or project systems.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants