rm-dev-workflows

dotnet port conflicts are resolved by inspecting active ports, terminating unsafe dotnet processes, and using Start-Process PowerShell to launch the site. This prevents mismanaged dev sessions and avoids bash timeouts on Windows.

Start the Blazor static web app by reading launchSettings.json to select the Watch or https profile. Use Start-Process powershell to launch the site, ensuring safe PowerShell process handling and avoiding bash command timeouts.

The best way to manage PowerShell processes for dotnet development is using Start-Process powershell to avoid bash timeouts. This approach ensures safe process handling, prevents port conflicts, and maintains recoverable Windows dev workflows.

Yes, browser tab hygiene is required during Windows dev workflows to keep sessions consistent and recoverable. Approved tool selection rules dictate how to manage browser tabs alongside file lookup and port checks for proper process management.

Your dotnet watch command times out in bash on Windows because bash cannot properly manage long-running Windows processes. Use Start-Process powershell to launch the site instead, which provides safe PowerShell process handling and avoids timeout issues.