Add ability to pin host port when debugging Dockerfile-based web apps in Visual Studio #460
Description
Description:
When developing and debugging web applications in Visual Studio using the "Container (Dockerfile)" profile, it is currently not possible to pin the host port (afaik). Visual Studio assigns a random high port on each run. This is a significant limitation when integrating with external identity providers (IDPs), such as when using OIDC authentication, because a static application port is required for redirect URIs.
Currently, the only workaround is to add Docker Compose support, which in turn requires the solution file (.sln) to be placed one level above all project files. In many real-world projects, restructuring the entire solution is not feasible, making this workaround impractical.
Impact:
- Debugging with external IDPs (e.g., ADFS, Azure AD, or any OIDC provider) is severely limited, as redirect URIs must be static.
- The current limitation reduces accessibility and flexibility for teams with established project structures.
Suggestion:
Please add the ability to specify and pin the host port directly in the Dockerfile-based debug profile (e.g., via launchSettings.json or project properties), without requiring Docker Compose or a specific solution file structure.