[github-actions]

Backport of #55899 to release/11.0.1xx

Collect generated rulesets, editorconfigs, global analyzer configs, and MSBuild integration files after generation and before NuGet gathers package files.

RC2 backport approval has been obtained. The servicing-approved label still needs to be recorded on this PR.

Customer Impact

• Customer reported
• Found internally

Published analyzer NuGet packages omit generated configuration and buildTransitive assets during clean one-pass packing. Direct-package consumers can silently lose expected diagnostics because analyzers do not receive required configuration/MSBuild properties, including inputs used by CA1416. Missing assets were confirmed in the inspected .NET 11 RC1 package. SDK-inbox integration copies these assets separately.

Reported in #54046 and #53125.

Regression

• Yes
• No

The generated assets are present in inspected earlier packages, including 9.0.0, but absent from sampled .NET 10 and .NET 11 RC1 packages. Generated-file globs were evaluated before their outputs existed.

Testing

The exact main-merge patch was applied to an isolated index based on release/11.0.1xx (6c212bd46ff54b103f32a6ab3e3c4ba7e8c677e1), without conflicts or whitespace errors. The backport workflow completed successfully.

No new regression tests are included in the source change. Release-branch CI, clean one-pass package-content inspection, and consumer validation remain pending. Validation should cover the expected rulesets, editorconfig, and buildTransitive assets, direct-package CA1416 analysis with inbox analyzers disabled, and the normal SDK-inbox path. Patch application is not a package-build or consumer-test result.

Risk

The change is limited to package asset collection timing in one project file; analyzer algorithms and default severities are unchanged. Restoring missing integration can surface previously missing diagnostics for package consumers, including build failures when warnings are elevated to errors. Clean-package and consumer validation are important to establish the restored behavior.

Note

This PR description was drafted with GitHub Copilot.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[tannergooding]

The corresponding 10.0.4xx and 10.0.1xx backports also exist:

• [release/10.0.1xx] Restore generated assets in Microsoft.CodeAnalysis.NetAnalyzers packages #56310
• [release/10.0.4xx] Restore generated assets in Microsoft.CodeAnalysis.NetAnalyzers packages #56311

Is the backport process for them the same as for other 10.0 repos? That is, I'll need to just send a mail to tactics after getting appropriate M2 sign-off?

[artl93]

Customer reported regression. Approved. Yes, Tactics for backports.