Uh oh!
There was an error while loading. Please reload this page.
Allow opting into ThisAssembly.Project via the ProjectProperty MSBuild property - #507
Merged
Conversation
kzu
enabled auto-merge (rebase)
August 27, 2026 01:43
kzuforce-pushed
the
dev/projectproperty-as-property
branch
from
August 27, 2026 01:44
8ca0199 to
cc003eaCompareMemberAuthor
🧪 Details on Microsoft Windows 10.0.26100from retest v1.1.0 on .NET 10.0.11 with 💜 by @devlooped |
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
File-based apps can set MSBuild properties with
#:property, but they cannot declareProjectPropertyitems.ThisAssembly.Projectonly emitted constants for those items, soThisAssembly.Project.MSBuildProjectDirectoryfailed to compile from an Aspire/file-based AppHost.PrepareProjectPropertiesnow includes$(ProjectProperty)as-is as@(ProjectProperty)items. Semicolon-separated names work the same as an itemInclude. File-based usage:Existing item-based opt-in is unchanged. Tests cover the property path with a semicolon-separated list.