Friday, July 25, 2014

Tip 7.29: How to customize your Error List view

"Visual Studio Tips, 251 ways to improve your Productivity in Visual Studio", courtesy of 'Sara Ford'

Sara Ford's Blog



Sara Aside

This was one of her least favorite designs in the IDE. When the Error List was split from the Task List in Visual Studio 2005, a row of buttons was put on the top of the Error List for users to customize whether they wanted to see just Errors, Warnings, or Messages. But, then again, it enables her to show you cool tips like Tip 7.32.


For example, here's the default with everything enabled.



And now, here's the Error List with nothing enabled, for dramatic effect.



Happy Programming! =)
Posted by Nils-Holger at 12:51 PM with 626 comments.

Thursday, July 24, 2014

Tip 7.28: You can use Ctrl+Shift+F12 to view the next error listed in the Error List

"Visual Studio Tips, 251 ways to improve your Productivity in Visual Studio", courtesy of 'Sara Ford'

Sara Ford's Blog



The keyboard binding is Ctrl+Shift+F12, and the command is View.NextError. She's a little surprised that there isn't a default keyboard shortcut for View.PreviousError. But you can always add one yourself.



And, of course, the status bar tries to be helpful by showing you the error you have navigated to. =)



Happy Programming! =)
Posted by Nils-Holger at 1:08 PM with 988 comments.

Wednesday, July 23, 2014

Tip 7.27: How to have all processes break when one process breaks

"Visual Studio Tips, 251 ways to improve your Productivity in Visual Studio", courtesy of 'Sara Ford'

Sara Ford's Blog



In Tools–Options–Debugging–General, there's the option Break All Processes When One Process Breaks.

Let's say you are debugging multiple projects, and you want to configure what happens when one process breaks.



For example, let's say she has two console applications running in an infinite loop. On the second console application, she breaks the process. If she has checked the Break All Processes When One Process Breaks check box, the first console application will break also.

And, of course, you can uncheck this option to have the first console application keep going.

Happy Programming! =)
Posted by Nils-Holger at 12:50 PM with 447 comments.