Skip to content

[New article]: Use EndpointProperty.HostAndPort in samples #2646

@afscrome

Description

@afscrome

Proposed topic or title

NA - updates to existing articles

Location in table of contents.

N/A

Reason for the article

dotnet/aspire#7629 introduces an EndpointProperty.HostAndPort to 9.2 that can simplify scenarios where you previously needed to concatenate Host and Port seperately - {foo.Property(EndpointProperty.Host)}:{foo.Property(EndpointProperty.Port)}

The docs currently have a few places that could use this simplification

$"smtp://{SmtpEndpoint.Property(EndpointProperty.Host)}:{SmtpEndpoint.Property(EndpointProperty.Port)}"

$"smtp://{SmtpEndpoint.Property(EndpointProperty.Host)}:{SmtpEndpoint.Property(EndpointProperty.Port)}"

$"smtp://{SmtpEndpoint.Property(EndpointProperty.Host)}:{SmtpEndpoint.Property(EndpointProperty.Port)}"

$"Endpoint=smtp://{SmtpEndpoint.Property(EndpointProperty.Host)}:{SmtpEndpoint.Property(EndpointProperty.Port)};Username={UserNameReference};Password={PasswordParameter}"

Article abstract

N/A

Relevant searches

Searching through the repo for .Property(EndpointProperty.Host)}:{ is how I found the above in case more of these show up in between creating this issue and the docs being updated for 9.2.


Associated WorkItem - 418801

Metadata

Metadata

Assignees

Labels

📌 seQUESTeredIdentifies that an issue has been imported into Quest.doc-ideaIndicates issues that are suggestions for new topics [org][type][category]

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions