dotnet/msbuild

Add support for `after.{SolutionName}.slnx.targets` for slnx solutions

Open

#12,166 建立於 2025年7月14日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)C# (5,062 star) (1,364 fork)batch import
Area: DocumentationArea: Solution (.sln)help wanted

描述

Summary

I stumbled on PR #11535 while working on a migration from .sln to .slnx. For me it seems to make sense that the after.{SolutionName}.slnx.targets should also work as it is an exact match to my solution name (including the extension). The documentation also says that both .sln and .slnx should work https://learn.microsoft.com/en-us/visualstudio/msbuild/customize-solution-build?view=vs-2022. I wonder why it was decided to not support the after.{SolutionName}.slnx.targets.

Background and Motivation

It seems unintuitive that the after.{SolutionName}.slnx.targets, an exact match to the solution name is not supported.

Proposed Feature

Add support after.{SolutionName}.slnx.targets instead of only the .sln variant.

Alternative Designs

No response

貢獻者指南

技術棧
csharp
領域
build systemtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of MSBuildUnderstanding of .sln and .slnx formats
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Review the referenced PR #11535 to understand why .slnx targets were excluded. Examine the MSBuild source code for solution file handling, likely in files like `SolutionFile.cs` or similar, to determine where to add support for `after.{SolutionName}.slnx.targets`. Look for relevant tests in the repository to ensure the new feature is covered.