Skip to content

Conversation

@benjaminpetit
Copy link
Member

Basic application to be used in the future container.

It relies on yarp nuget packages for now because of the dependency to aspire service discovery.

<PropertyGroup>
<OutputType>Exe</OutputType>
<RuntimeIdentifiers>win-x64;win-arm64;linux-x64;linux-arm64;</RuntimeIdentifiers>
<TargetFramework>net8.0</TargetFramework>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<TargetFramework>net8.0</TargetFramework>
<TargetFramework>net9.0</TargetFramework>

If we're the only ones expected to build this, can we just always use the latest?

Copy link
Member Author

Choose a reason for hiding this comment

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

We are the only one, but since it will be used in a Dockerfile in another repo, I prefer keeping the target framework explicitely fixed

Copy link
Member

Choose a reason for hiding this comment

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

If you mean hardcoding the TFM instead of using the variable, that's fine by me.
I was mainly asking about 8.0 vs 9.0.

I see you currently have it build both - how come not just 9.0?

@benjaminpetit benjaminpetit merged commit 093ed77 into dotnet:main Jan 10, 2025
7 checks passed
@MihaZupan MihaZupan modified the milestones: Backlog, YARP 2.3 Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants