Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ Uses the .NET SDK (`dotnet` CLI). Key files:
- `global.json` — pins .NET SDK and Workload versions
- `Directory.Build.props` / `Directory.Build.targets` — shared MSBuild properties across all projects

### MSBuild hierarchical structure

MSBuild searches upward from each project file and uses the **nearest** `Directory.Build.props`/`.targets` it finds. Parent files are not automatically included. props/targets files in this repo explicitly `<Import>` parent/root files when appropriate.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: link to Microsoft docs

Shall we have a markdown link to the MSBuild docs?
https://learn.microsoft.com/visualstudio/msbuild/customize-by-directory?view=visualstudio#directorybuildprops-and-directorybuildtargets

Or would links in AGENTS.md just clutter the context?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The risk is that it follows the link, which will slow it down and add way more context than we really want... so no, I don't think we want to do that. If it keeps stuffing things up re props/targets files even with these instructions, I think we should look at improving these summary/concise instructions rather than linking to docs that are designed to be read by humans.


`integration-test/Directory.Build.props` / `integration-test/Directory.Build.targets` are intentionally isolated (do not import root).

## Solution Filters

Use solution filters instead of the full `Sentry.slnx`:
Expand Down
Loading