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

Console output is not visible in visual studio when using AspNetCoreHostingModel set to InProcess #6609

Open
yepeekai opened this Issue Jan 11, 2019 · 7 comments

Comments

Projects
None yet
4 participants
@yepeekai
Copy link

yepeekai commented Jan 11, 2019

Describe the bug

The output of the web application is no longer visible in the output of visual studio (ASP.NET Core Web Server) when using InProcess IIS hosting (webapp.csproj => InProcess)

To Reproduce

Steps to reproduce the behavior:

  1. Create a new asp.net core web application in visual studio
  2. By default AspNetCoreHostingModel is set to InProcess in the csproj
  3. Execute the web app
  4. There is no entry available in output to see ASP.NET Core Web Server output

Expected behavior

The ASP.NET Core Web Server output should be available and we should see the output log of the web app

Additional context

I am using asp.net core 2.2.1
If I change the value of AspNetCoreHostingModel to OutOfProcess, everything works as expected

@jkotalik

This comment has been minimized.

Copy link
Member

jkotalik commented Jan 11, 2019

Can you check the Output window "Show output from: Debug"?

@yepeekai

This comment has been minimized.

Copy link
Author

yepeekai commented Jan 11, 2019

yes that works when you start debugging the web application. Thanks for that workaround. But this doesn't work when not in debug as it used to when using outofprocess...

@muratg muratg added the servers-iis label Jan 11, 2019

@muratg

This comment has been minimized.

Copy link
Member

muratg commented Jan 11, 2019

@BillHiebert @vijayrkn Thoughts on this?

@BillHiebert

This comment has been minimized.

Copy link

BillHiebert commented Jan 11, 2019

@muratg whenrun out of process, Visual Studio inserts a "shim" process between IIS and the users application, The shim starts the user process, connects to stderr\stdout and redirects it to a pipe opened by VS. Inprocess does not have the shim process so it doesn't pick up up the outputs. Since we start the IIS Express process, we could look into grabbing its output and showing it in the window..

@jkotalik

This comment has been minimized.

Copy link
Member

jkotalik commented Jan 11, 2019

I think piping the output of iisexpress would just "work". We do it in functional tests today.

@yepeekai

This comment has been minimized.

Copy link
Author

yepeekai commented Feb 13, 2019

Out of curiosity, is this issue gonna be resolved in the upcomming asp.net core 3 release?

@BillHiebert

This comment has been minimized.

Copy link

BillHiebert commented Feb 13, 2019

It is fixed in the next preview of VS 2019.

@muratg muratg added this to the Discussions milestone Feb 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment