This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm developing a Blazor Server App which interfaces with an API I have built.
At one point, my project was set up to open a Windows Console output window which showed essentially the same info as the Output window in VS but also the content of my Console.Writeline() commands as well. I'm not sure if this stopped as a result of a change I have made to the environment or the project settings but that Windows Console window no longer launches when I debug my app in VS.
If anyone knows what I'm referring to, has had it and solved the issue or knows the way back I would love to hear from you. It's been driving me insane with frustration! It was my go-to debug solution!!
Thanks everyone.
Flic
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 11%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hi FelicityWinter,
You can go to Project Properties > Application, then check if the output type is Console Application.
Best Regards,
Dylan
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our **documentation to enable e-mail notifications if you want to receive the related email notification for this thread.**
Thanks Dylan, I had tried that from other posts but no luck I'm afraid.
I haven't spent much more time investigating as I've managed to solve the VS Output view for capturing my debug notes but I'd sure love my separate semi-transparent console window back! I have also considered that while I'm running both Community Standard as well as Preview, the fact I'm developing a Net 6 Preview app might have something to do with it as well maybe.
Hi @Felicity Winter , you can try to run {Your App} instead of IIS Express
Perfect! Well, almost. I'm more than happy with this solution and thank you so much @Dylan Zhu-MSFT I won't forget this in future! I note that I used to have my API and Server app (same project) start together as well as the console window but now you've shown me how to achieve the same result I'm just as happy. Thank you! 🙏
Dylan you have actually resolved my original issue for me with your answer. I can expand on your solution after further experimenting.
My issue: One solution containing two projects, a Net Core Web API and Blazor Server Client. At one point when I debugged my solution with both apps starting, a console window would open allowing me to write debug messages from my server client to it. After a Windows Insider update and new VS builds I could not replicate my previous experience and I have seen numerous cries for help on the same issue online.
The fix care of Dylan: The project inside your solution that you wish to have an accompanying console window for should be run as shown in Dylan's screenshot above. This will invariably open a console output window. It appears that so long as you do this the first time, you can then set your multiple projects to start up and the console window will load for the desired project or remain open from the previous debug and continue on.
Note: I have not tested this across multiple projects but have replicated my description above several times after rebooting.