Skip to content

Skeleton app for containerization#2710

Merged
benjaminpetit merged 4 commits intodotnet:mainfrom
benjaminpetit:container-base
Jan 10, 2025
Merged

Skeleton app for containerization#2710
benjaminpetit merged 4 commits intodotnet:mainfrom
benjaminpetit:container-base

Conversation

@benjaminpetit
Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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?

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