-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DockerLaunchAction seems to depend on log to start browser #323
Comments
@mathysd I've opened a PR to add docs for a work-around for this when debugging a single project in a container: MicrosoftDocs/visualstudio-docs#7541 Using the Launch Profile property |
Any update on that? We are using structured loging so we don't have that phrase at all it's broken out. So levels don't help. |
@dmikov As now documented in: https://learn.microsoft.com/en-us/visualstudio/containers/container-launch-settings there is now a launch profile property |
Just in case a lost soul ends up here looking for a solution: An example of setting logging levels in docker-compose.yml:
Similar in appsettings.json or appsettings.Development.json
|
LaunchBrowser won't work if the log setting for
Microsoft.Hosting.Lifetime is not set to information. Visual studio seems to wait for Now listening on: http://[::]:80 before actually launching a browser. No warning or error is written anywhere. So it took my quite some time to figure this one out.
I added docker and docker-compose to an existing project. This project uses serilog with serilog request logging (UseSerilogRequestLogging) and all microsoft logging is set to Warning.
Originally entered by @mathysd as https://github.com/MicrosoftDocs/visualstudio-docs/issues/6441
The text was updated successfully, but these errors were encountered: