Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unexpected blank lines when dotnet new foo --help run in PowerShell
See original GitHub issueDoing dotnet new razor --help with PowerShell in full screen renders nicely but when executed with a smaller PowerShell window, lots of blank lines appear:
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Remove blank lines in powershell output... Generally
You can define a custom Out-Default function that removes all empty/blank lines from the output (for display only):
Read more >Blank lines in powershell throwing "The Term '' is not ...
I'm at my wit's end. My google-fu is failing and I'm not finding solutions to rectify this issue. This tends to happen when...
Read more >Windows PowerShell Cheat Sheet
Windows PowerShell Cheat Sheet. This document requires a browser that supports JavaScript.
Read more >Azure CLI failing from microsoft hosted agent
We are running the below powershell command in the Azure CLI task and the same was working 2 ... Error: ERROR: The command...
Read more >Performance Improvements in .NET MAUI
Want to know why .NET MAUI apps boot faster, run smoother, and are smaller? This post break down how we made .NET MAUI...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue was fixed in .NET 7.0.1xx preview2.
@RehanSaeed we plan to start work on moving to new parser next month (https://github.com/dotnet/templating/issues/2520). New parser features different help output and it should not have this problem.