Copy App-Host for a self-contained app with extension only on windows #1378
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Customer scenario
Publishing self-contained apps that have a "." in their name ends up publishing an executable with the wrong name.
When copying the App-Host for a self-contained app, only use the extension when publishing for windows. Otherwise, for apps with a . in the name, the part that comes after the . ends up being used as an extension and the executable has a duplicated last piece of the name, like sample.console.console, instead of sample.console.
Bugs this fixes:
Fixes https://github.com/dotnet/cli/issues/6397
Workarounds, if any
Change the name of your application or hack some msbuild to change the file name after it is copied. It is bad.
Risk
Low
Performance impact
None
Is this a regression from a previous update?
Yes.
Root cause analysis:
Lack of test coverage.
How was the bug found?
Reported by the community.
@livarcocc @dotnet/dotnet-cli for review
@MattGertz for approval