C# Visual Studio 2005 full set of 'DEBUG' buttons missing in taskbar

Hello everyone,

This should be a simple one.

Visual studio 2005 is running fine, but I don't see some of the Debug Buttons
that I was used to in the VS2003 version.

I tried adding them to the task bar - but I don't see the category.

Maybe some else has fixed this too.

Thanks
paygoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

2266180Commented:
Maybe I am not understanding you right since I don't have vs2005, but aren't you looking for the toolbars?

you can set them visible or not by going in the menu -> view -> toolbars -> debug

isn't that it, or am I missing something?
bruintjeCommented:
Hello paygo,

you can also customize the toolbar
if you rightclick on the toolbar, on the toolbar tab be sure to check the debug box, then goto the commands tab and again in the first list choose debug no on the right listbox all debug commands appear and you can add them to the debug toolbar

hope this helps a bit and a happy new year!
bruintje
paygoAuthor Commented:
Thanks for the help - All the options I have are

1 continue
2 Break All
3 Stop debugging
4 restart
5 step over
6 window

Still missing most of the ussual step buttons - step into etc
OWASP: Avoiding Hacker Tricks

Learn to build secure applications from the mindset of the hacker and avoid being exploited.

paygoAuthor Commented:
command tab?  - is this the tab all the way to the right fo the task bar?
bruintjeCommented:
if you rightclick on a debug icon do you get a list of toolbars? if yes then the last option is cusotmize from there you can use the dialogs to change the appearance of the debug toolbar

if no, please post back
2266180Commented:
after you have made the toolbar visible, you will notice that it has a small black triangle at it's right end pointing down. if you move your mouse over it, the tool tip will say "Toolbar options". clicking on it will show a menu "add or remove buttons", clicking on/moving the mouse over it will show a set of menus, including "debug". clicking on this "debug" menu will show in a list all the possible buttons that can apear on the toolbar. by default they are all checked. if this is not you case, then check the buttons you want to be displayed by clickin gon them. notice that most of them will be grayed out (disabled) since you are not running any project ;)

hope this helps
alpesh_mcaCommented:
Hi  paygo,

Debug Symbols

What are debug symbols? Debug symbols are vital for a successful debugging session. Debug symbols help the debugger correlate instructions in your application back to file names and line numbers in your source code. Debug symbols are stored in a program database file with a .pdb extension. Without a .pdb file present, you won’t be able to step through the lines of code in your application.

When you create a new project with Visual Studio .NET, you’ll find the IDE creates two build configurations for your application (unless your project is a web project). You can see these configurations under the Configuration option of the Build menu. There is a Release configuration, which compiles your application so that the application will run as efficiently as possible. There is also a Debug configuration. The debug configuration compiles your application for the best debugging experience. In addition to creating PDB files, a debug build will also disable optimizations. Compiler optimizations will often rearrange instructions to increase performance or reduce memory consumption. The rearrangement of instructions can confuse the debugger.

For ASP.NET web applications and web services, you can enable a debug build in the compilation settings of web.config. Alternatively, if you pre-compile your application, you can use flags with the pre-compilation tool to generate .pdb files with debugging symbols
1.  Breakpoints

Debugging is all about collecting information and finding out what is wrong in your application. Part of the trick in collecting information is pausing, or breaking into the execution of your application at just the right spot. When the debugger is in break mode, you can examine objects and local variables to see what is going awry. We use breakpoints to tell the debugger where and when we want to pause the execution of our application.
2. Conditions and Hit Counts

Most of the time you’ll add a plain breakpoint to an application and not set any special properties. If you open up the breakpoint window (from the Debug menu, select Windows -> Breakpoints), you’ll notice a breakpoint can use conditions and hit counts. Conditions and hit counts are useful if you don’t want the debugger to halt execution every time the program reaches the breakpoint, but only when a condition is true, or a condition has changed, or execution has reached the breakpoint a specified number of times.

3. Breaking On Exceptions

Another way to halt execution of a program is to ask the debugger to break when an exception occurs. By default, the debugger will only break if the exception goes unhandled, but this behavior is configurable. Select Exceptions from the Debug menu and you’ll see a tree display of all possible exceptions alongside checkboxes to indicate if the debugger should break when an exception “is thrown”, or only break if the exception is “user-unhandled”.

4. Stepping Through Code

Once you pause execution you have the ability to step through code, in other words, execute code one line at a time. From the debug menu there is a Step Into command (F11) . If you are currently in break mode on a line of code that contains a method call, the Step Into command will enter the method and break again on the first line of code inside the mehtod. In contrast, the Step Over command will execute the entire method call and break on the next line of code in the current method. Use Step Into if you want to see what happens inside a method call; use Step Over if you only want to execute the entire method and continue in the current code block.

5. Viewing State
Another crucial feature to have in a debugger is the ability to see and visualize the data in your application. Fortunately, Visual Studio offers plenty of options to view data, and to customize the views of data.
DataTips

One of the common techniques to view the data inside a variable is to place the mouse cursor over the variable in code and allow Visual Studio to display a DataTip. DataTips are only available when the program is in break mode.

6. Variable Windows
DataTips are a transient display of information – once your mouse leaves the DataTip area the DataTip display will disappear. If you want a permanent display of an object’s value you can use one of the many variable windows.

7. Visualizers
A visualizer is a new way to view data in Visual Studio 2005. Some dataypes are too complex to display in a DataTip or watch window. For example, a DataSet is a tremendously complex and hierarchical object. Trying to drill into the 5th column of the 10th row of the 2nd table of a DataSet is cumbersome. Fortunately, a Visualizer exists for DataSet objects that will display the data in a more natural environment, namely an editable data grid.

8. Wrap Up
When your program is buggy, Visual Studio will give you all the tools you need to track down the error. Control the execution of your application with breakpoints, and use variable windows, data tips, and visualizers to inspect state along the way.

To know more things related with debug with images please refer following links:
http://odetocode.com/Articles/425.aspx
I hope this is what you are looking for.
All the very best.
Thanks.
Alpesh Patel.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
alpesh_mcaCommented:
one more link:
http://lab.msdn.microsoft.com/express/vcsharp/develop/debug/default.aspx
I hope this is what you are looking for.
All the very best.
Thanks.
Alpesh Patel.
paygoAuthor Commented:
Here's the correct answer - for my question

1 - Go to the existing toolbar and cursor overto the DEBUG options - Right Click

2 - A large drop down menu appears - At the bottom select customize.

3 - A new list box appears - make sure the COMMANDS TABn is clicked.

4 - Two panes appear:  Left Pane CATEGORIES   Right Pane COMMANDS

5 - from the Left Pane select 'Debug' - and all the possible Debug Icons / Symbols
     appear in the COMMANDS Pane (right Pane)

6  - Now 'Drag and Drop' and Icon/Symbol on to your Debug Toolbar (up top)


Thanks everyone for the help - I 'll split up the points





 
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.