Applicationurl shouldn't randomly generate port 5060 or 5061

[sammychinedu2ky]

I noticed a little error.
Port 5060 and 5061 aren't allowed by new browser versions due to the natslip attack (https://chromestatus.com/feature/5064283639513088). Port 5060 was randomly created for me in the launchSettings.json file which made me have issues accessing my API from the browser. I had to change the applicationUrl port manually.

if I can be shown the line where the port generation is done in the dotnet SDK, I would also appreciate it. Thanks

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[sammychinedu2ky]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@Tratcher

[Rick-Anderson]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

The SDK team will take care of that.

[kasperk81]

similar change/discussion dotnet/runtime#76485.
@pavelsavara

[javiercn]

This would affect pretty much all our templates

[kasperk81]

@javiercn do you know where is the random port generation happening? i can't find anything like that in this repo.

[mkArtakMSFT]

@vlada-shubina do you own the templating engine? This change should be done there and I'm not sure if this should move to dotnet/templates or somewhere else?

[mkArtakMSFT]

@SteveSandersonMS found where the code for port generation is so I'm moving this over to that repo: https://github.com/dotnet/templating/blob/main/src/Microsoft.TemplateEngine.Orchestrator.RunnableProjects/Macros/GeneratePortNumberMacro.cs

[sayedihashimi]

cc @phenning and @vijayrkn this may also impact Visual Studio scenarios