Ladies and gentlemen, we have finally reached the holy grail of debugging!
I don’t know whose idea it was not not mention this during today’s Connect(); event, but here’s one new feature of Visual Studio 2015 that, personally, I feel should have made the keynote. …Continue reading “Debugging Lamda Expressions with Visual Studio 2015” [Debugging Lamda Expressions with Visual Studio 2015]
I recently put in an application to become a Pluralsight author (www.pluralsight.com). I’m hoping they’ll read this and know that I’m very serious about making this happen. I really believe I’m capable of making really great videos for what is already the world’s best resource for developer training.
So, hello Pluralsight application reviewer person! Let’s be friends! :)
This is the second time I’ve wanted to get Grows for Windows working with Visual Studio 2013.
The Visual Studio plugin hasn’t been updated since since 2010, so it takes just a little bit of effort to get it working
The key, every time I do this, is to find this old post.
You may have noticed hat post talks about fixing the plugin to work in Visual Studio 2012. Of course, making it work in 2013 is about as simple as you can imagine.
- Install the current Growl For Visual Studio plug in
- Open up %APPDATA%\Microsoft\MSEnvShared\Addins\GrowlExtras.VisualStudioAddIn.AddIn in notepad
- In the <Extensibility> node, add the following
<Name>Microsoft Visual Studio Macros</Name>
<Name>Microsoft Visual Studio</Name>
- Save and close the file
- Might have to close and restart Visual Studio for it to actually register with Growl.
We devs… We write code, save, flip over to the browser, press F5 to refresh the page… and wait. And wait. And probably wait some more.
That’s no way to live. Some sites can take quite a while for the page to load, typically due to background processes that need to get warmed up before the site beings to act smoothly.
Personally, I want to be doing other things while I wait for that page to load. But I don’t want to forget that I was ever waiting for the page to load. I want an audible notification that the page was ready for me to work with. And I want it to be a generic tool I can tweak to work with any website/page I’m working on, without having to modify the actual website.
And so I installed Tampermonkey in Chrome. I guess it’s like Greasemonkey, but I’ve never used that either. :)
Turns out, I was able to get exactly what I want relatively easy.
I don’t even understand how that beep() function works, but it does. The important thing is the @match line at the top that instructs Tampermonkey to run the beep function when that page is finished loading.
Now I can press CTRL+F5 in VisualStudio and switch over to responding to emails until I hear the beep that lets me know the webpage has finished loading.