Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

pavelsavara
Copy link
Member

@pavelsavara pavelsavara commented Sep 3, 2025

D:\a\_work\1\s\artifacts\bin\System.Text.RegularExpressions.Tests\Release\net10.0\browser-wasm\publish\NuGet.Common.dll in the publish binlog is bad. Because it makes CI build slower.

image

PrivateAssets="All" means exclude from publish

https://github.com/dotnet/sdk/blob/74ee5e8b76b4b564657b3f6a2051c05eaae68ddc/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.Shared.targets#L50-L60

Fix for #119317

@pavelsavara pavelsavara added this to the 11.0.0 milestone Sep 3, 2025
@pavelsavara pavelsavara self-assigned this Sep 3, 2025
@pavelsavara pavelsavara added the code-analyzer Marks an issue that suggests a Roslyn analyzer label Sep 3, 2025
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 3, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Sep 3, 2025
@pavelsavara pavelsavara added area-Build-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Sep 3, 2025
@pavelsavara pavelsavara force-pushed the dont_publish_analyzers branch from 0144ca8 to 6a795a2 Compare September 3, 2025 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Build-mono code-analyzer Marks an issue that suggests a Roslyn analyzer linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant