[Console]::Beep() does not activate "Bell Notifications" about terminal

[DHowett]

Thanks for filing! Unfortunately (and I really do mean unfortunately - this bug makes me sad), the .NET runtime or the PowerShell console adapter actually implemented Beep as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹

[GarThor]

Thanks for filing! Unfortunately (and I really do mean unfortunately - this bug makes me sad), the .NET runtime or the PowerShell console adapter actually implemented Beep as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹

Bummer, I kinda figured it was something like that, but I figured it wouldn't hurt to ask.

[lhecker]

I just checked the latest .NET code and it's still true today:
https://github.com/dotnet/runtime/blob/039d2ecb46687e89337d6d629c295687cfe226be/src/libraries/System.Console/src/System/ConsolePal.Windows.cs#L656-L673

Because of this this bug unfortunately needs to be reported over at https://github.com/dotnet/runtime, if anything 😕.

[GarThor]

I just checked the latest .NET code and it's still true today: https://github.com/dotnet/runtime/blob/039d2ecb46687e89337d6d629c295687cfe226be/src/libraries/System.Console/src/System/ConsolePal.Windows.cs#L656-L673

Because of this this bug unfortunately needs to be reported over at https://github.com/dotnet/runtime, if anything 😕.

rad, thanks... I'll try over there.

[lhecker]

Thanks for filing it! I'm not familiar with .NET development, but as a terminal maintainer I do hope you have success. Other platforms use "`a" already (if you check out the other ConsolePal.*.cs files), so it IMO makes sense if Windows does too, even if it's only in the next big .NET version.
Maybe the best approach is to just make Beep() print "`a" while Beep(int, int) continues to use the kernel32 implementation.