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 I have two console applications running in an infinite loop. And on the second console application, I break the process. Notice how the first console application also breaks.
And of course, you can unchecked this option to have the first console application keep going.
Technorati Tags: VS2005Tip,VS2008Tip
Yesterday’s tip talked about how to start multiple projects for debugging, but taking a step back, let’s talk about the two ways you can select a single startup project.
The first way is via the solution property pages. Right-click on the Solution, and under Common Properties-Startup Project, you can choose “Single startup project”. here you can select the project.
Or for the real tip for the day, you can right-click the project and select “Set as StartUp Project” from the context menu.
The startup project will be bolded in the solution explorer.
Happy Birthday Visual Studio Tip of the Day! Wow, what a difference a post a day makes. Thanks to everyone who has been reading the series. It’s been an extremely rewarding experience to see these tips help.
And thanks for the motivation to continue writing. It takes me on the average 20-30 minutes to decide what tip to write, to capture the screenshots, and to add it to the queue. I refuse to do the math. I just don’t want to know. =D
I consider July 27, 2007 to be the kick-off day for Tip of the Day, since that’s when I posted #002 and started the consecutive series. #001 went out a few days earlier for us to get the RSS feeds ready to go. I wished Tip of the Day happy birthday while presenting at OSCON, even if it wasn’t the targeted audience. =D
If you are only using one project per solution, today’s tip may not mean too much to you. But, if you have multiple projects, you can select which ones of them you want started under the debugger.
Right-click the Solution in the Solution Explorer, and select Properties. Go to the Common Properties – Startup Project page (it’s the first page in the dialog).
You’ll see three radio buttons:
And using the example above, when I hit F5, I get
Technorati Tags: VS2005Tip,VS2008Tip
Yesterday’s tip talked about how to delete all breakpoints. If you are following along at home, you hit the warning message that appears when you attempt to do this.
If it is annoying, you can disable it by going to Tools – Options – Debugging – General, and uncheck the Ask before deleting all breakpoints checkbox.
Technorati Tags: VS2005Tip,VS2008Tip
If there ever were a “Sara needs a hug” moment… I’m doing a talk on Friday called Towards a Stronger Open Source Ecosystem. It’s a story about what I’ve seen and ideas I have for the future. I actually put together this abstract 2 years ago, so it isn’t necessarily a talk about the future of CodePlex, as my day job would led you to believe.
Here’s the abstract. Wish me luck!
“Code speaks louder than words” is a fundamental philosophy of the open source community, because developers use code to discuss code, not words. Imagine a code review over email that did not contain a single line of code. The conversation would be lost in translation. Code is the universal language in the developer ecosystem, allowing us developers to communicate with one another.
But yet, we don’t communicate universally today. We define ourselves by our business models, our developer tools, our technologies, hence defining who we converse with. But imagine if there were no definitions or boundaries, where all developers could effectively engage together. Imagine an open source ecosystem that included all developers, regardless of platform, language, or development environment.
This talk will cover go over a roadmap for striving towards this stronger open source ecosystem through current infrastructure enhancements, fostering community growth through discoverability, project incubations and sponsorships, and paving the ways for proprietary products to evaluate various methods of going open source.
In the general development settings, I didn’t see this command under the Debug menu. So, in case you want to use the keyboard to enable or disable a breakpoint, you can Ctrl+F9, which is bound to the command Debug.EnabledBreakpoint. Note that you won’t find a Debug.DisableBreakpoint, since this is handled by the enabled command.
A disabled breakpoint will still get saved in your Breakpoints window, but will be ignored while debugging.
Technorati Tags: VS2005Tip,VS2008Tip
In the New Breakpoint window, there’s a checkbox “Use IntelliSense to verify the function name.” Just as you would expect, this does a sanity check to ensure the function name is valid in your project.
For example, if the function name doesn’t match an overload, you’ll get prompted to choose which method you really meant.
Or if the function doesn’t exist,
Now, let’s say you don’t need its help and uncheck the option. In the case above, a breakpoint will be inserted in all overloads for the function. Or if you type in a function that doesn’t exist, it won’t get inserted into the code, but will get created in the Breakpoints window.
Technorati Tags: VS2005Tip,VS2008Tip
In case you want to set a breakpoint at a given function, and not at the current line, you don’t have to search for the function name to hit F9. You can press Ctrl+B (general development settings) to do a Debug – Break at Function.
This command will bring up the Breakpoint window.
Here you can type in the name of the function you wish to set a new breakpoint at.
Technorati Tags: VS2005Tip,VS2008Tip
