'How do I get notification that the local Visual Studio build is complete?
There doesn't seem to be a post-build solution task. One could presumably hack it by creating a dummy project that is the last one to build and put a beep in the post-build project.
Solution 1:[1]
There is Visual Studio Ding extension.
This small extension will play notification sounds when following events occur:
- Build Complete
- Entering debugger mode (breakpoint hit, etc)
- Unit tests finished to run
https://visualstudiogallery.msdn.microsoft.com/941d0ed0-1218-452e-8585-d3ac693cda17
Solution 2:[2]
The ToastNotifier Extension seems to work well for visual feedback.
Solution 3:[3]
Go to Start -> Control Panel -> Sounds and Audio Devices. Then on the Sounds tab you'll find a set of sounds for Microsoft Visual Studio in the Program Events list. You can attach a sound to build finishing, etc.
Solution 4:[4]
You could write a simple .bat file that you could add to the post-build events...
Here a link: Pre-build Event/Post-build Event Command Line Dialog Box
Solution 5:[5]
I have used this.
It's pretty neat for visual notification, while the options posted by others are all fine for audio.
Solution 6:[6]
Personally I just have the "Output" window turn on by default and don't use the task list. This way I can see what it is doing at all times. I find the messages from this window to be much more enlightening than the task/error list.
Solution 7:[7]
I use Growl with visual studio add on. It's also working with VS2013 by using this tweak.
Solution 8:[8]
You can also now as of VS2019 gain access to the system sounds through the UI. Go Options->Test.
You can also find more info out here: https://docs.microsoft.com/en-us/visualstudio/test/run-unit-tests-with-test-explorer?view=vs-2019#test-audio-cue
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | vmg |
| Solution 2 | Bryan Matthews |
| Solution 3 | David Norman |
| Solution 4 | bytebender |
| Solution 5 | µBio |
| Solution 6 | Joel Lucsy |
| Solution 7 | BornToCode |
| Solution 8 | Alex D |

