-
Notifications
You must be signed in to change notification settings - Fork 863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skeleton app for containerization #2710
Conversation
<PropertyGroup> | ||
<OutputType>Exe</OutputType> | ||
<RuntimeIdentifiers>win-x64;win-arm64;linux-x64;linux-arm64;</RuntimeIdentifiers> | ||
<TargetFramework>net8.0</TargetFramework> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
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.