fix: add self contained config in dotnet publish

[zidaneymar]

Description

Under linux environment, webapp bot couldn't be started up after dotnet publishing.
This issue only occurs at 'linux' env.
For runtime identifier: please refer to this doc: https://docs.microsoft.com/en-us/dotnet/core/rid-catalog

Task Item

fixes #4348

Screenshots

[luhan2017]

Can we add an param for deployment, and default it to windows? Later if customer want to have a customized deployment (for example, linux vm), they can just set the param in the script.

[zidaneymar]

Can we add an param for deployment, and default it to windows? Later if customer want to have a customized deployment (for example, linux vm), they can just set the param in the script.

OK, I will add it today.

[coveralls]

Coverage remained the same at 55.362% when pulling 63f1253 on qika/fixRuntime into b2cd261 on main.

[cwhitten]

@zidaneymar @luhan2017 I'd like to verify that this won't break existing publishing profiles without this new shape, and allow users with old publishing profiles to add this new parameter.

[zidaneymar]

Tested 4 different scenarios:
Composer hosting on linux publish to linux operating system.
Composer hosting on linux publish to windows operating system.
Composer hosting on windows publish to linux operating system.
Composer hosting on windows publish to windows operating system.

[luhan2017]

@zxyanliu, this may need a doc update, users needs to understand what this field means and how to use it.

[zxyanliu]

luhan2017 commented 7 hours ago
@zxyanliu, this may need a doc update, users need to understand what this field means and how to use it.

No problem, let's discuss in detail offline.