[release/7.0] Web.ProjectTemplates: exclude 'Program.cs' from all templates that replace it.

[github-actions]

Backport of #46769 to release/7.0

/cc @captainsafia @tmds

Web.ProjectTemplates: exclude 'Program.cs' from all templates that replace it.

Summary of the changes (Less than 80 chars)

Description

{Detail}

Fixes #{bug number} (in this specific format)

Customer Impact

{Justification}

Regression?

• Yes
• No

[If yes, specify the version the behavior has regressed from]

Risk

• High
• Medium
• Low

[Justify the selection above]

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.1

• Make necessary changes in eng/PatchConfig.props

[ghost]

Hi @github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no breaking changes are introduced, please leave an /azp run comment here to rerun the CI pipeline and confirm success before merging the change.

[mitchdenny]

Approved, although do we want this in for the next servicing release?

[captainsafia]

Approved, although do we want this in for the next servicing release?

Yep, missed the cut-off for the last release.

[RussKie]

We expect to merge this in early April (when branches open), right?

[captainsafia]

We expect to merge this in early April (when branches open), right?

Yep, I'll send the servicing request for it at that time as well.

[wtgodbe]

@captainsafia can you get servicing approval for this?

[captainsafia]

@captainsafia can you get servicing approval for this?

I was OOF during the first couple of days of the servicing window. I'll see if I can get approval by 4/10 for this.

[captainsafia]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[captainsafia]

@tmds What's the best way to verify this change manually? I'm not sure how to reproduce the bug in the current version of 7.0 to verify that we fixed the behavior here...

[tmds]

@captainsafia this reproduced always on our CI server and, I think, on my machine as well. I don't know how you can make it reproduce on an environment where it is not reproducing by default.

If you want, I can see if the 7.0 branch reproduces this issue on my machine before this patch, and after.

Anyway, the template experts (that chimed in on the PR) confirmed the behavior was not deterministic the way it was previously defined.

[ghost]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no breaking changes are introduced, please leave an /azp run comment here to rerun the CI pipeline and confirm success before merging the change.

[captainsafia]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ghost]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no breaking changes are introduced, please leave an /azp run comment here to rerun the CI pipeline and confirm success before merging the change.

[captainsafia]

@captainsafia this reproduced always on our CI server and, I think, on my machine as well. I don't know how you can make it reproduce on an environment where it is not reproducing by default.

If you want, I can see if the 7.0 branch reproduces this issue on my machine before this patch, and after.

Anyway, the template experts (that chimed in on the PR) confirmed the behavior was not deterministic the way it was previously defined.

I followed up with @vlada-shubina about this. Considering it happens on certain flavors of Linux and hasn't been reproduced outside of CI, it isn't worth taking through tactics for servicing at this moment.