Hi,

The documentation is the best place to look.

This document explains the debug speed, port, pin options and also contains a link to the project properties documentation.

Debugging with Different Ports, Pins and Speeds
Documentation Index
Project Properties

You haven't said which Ide you are using but if it is VS normally you click the project and press F4. Don't be confused with the "Property Pages". The "Project Properties" is a tool window.

If you look at the title of your screen shot it says "Property Pages" and I specifically noted that would be the wrong window (although maybe not very clearly). 

Property pages is a dialog window  and not what you want. Tool windows like "Project properties" are windows that can be docked and tabbed like the solution explorer and output windows.

Close the dialog you have on the screen. Please submit a screen shot of your ide with the project open (and selected in the solution explorer).

Then I will tell you what to click

Tim@Visual Micro wrote on Aug 25^th, 2015 at 4:20pm:

Assuming you are one of the Visual Micro developers....


OK well I have been through a bit of this at my last IT job at Tabcorp in Victoria, Australia. I was given the job of writing a user manual for the testers explaining how to install the software on a new Easybet terminal by ghosting from another hard disk.

I made all the same mistakes about the amount of knowledge I already had with this sort of process. My first attempts were basically unusable by the testers.

I had to place myself in the position of a brand new employee in the testing department who had no knowledge of ghosting a hard disk.

In the end the document was fully detailed step by step instructions with screen shots at nearly every step.

It was a laborious process to write the manual but in the end, if it is about excellence rather than duty to be endured, then it is worth while creating a high quality user manual.

So you have collectively assumed that I know, as a new user, precisely what you mean by 'project => properties' (i.e. literally through the menu structure) when apparently that is not the case.

So my suggestion is to add the missing details to your website help pages assuming that your reader perhaps had not even used Visual Studio before.

Here is the screen shot you asked for:

Press f4

OK I stumbled upon the right button - it is the second one after the combo box containing "typdef unit16".

I.E. Popup hint "Properties Windows" And the short cut in VS 2010 is ALT + ENTER, not F4.

A suitable screen shot with a red circle around that button, on those help pages of yours, would make it a great deal easier for the next person that runs into this problem.

Off-Topic replies have been moved to this Topic.

I have been looking here: http://www.visualmicro.com/page/Debugging-for-Arduino.aspx

And a few other pages I found with your search function.

Perhaps what you need is a single debugging page with step by step instructions and with all the relevant info pertaining to debugging in one place.

When I say step by step, I mean step by step to the nth degree assuming that your reader knows nothing beyond the native arduino IDE and perhaps very general usage of VS.

What you seem to have is bits of information on different pages so that for me, as a new user, it is totally confusing.

And if I was creating a user manual I would be listing all the ways you can get to the project property page, not just one.

If the keyboard short cuts vary between different versions of VS then perhaps it is not really worth mentioning at all. As long as you detail right click method and the toolbar method (probably the same from VS 2010 on) then most windows users will soon figure out what the keyboard short cut is for their VS version.

With respect to these suggestions....take it or leave it. But it would sure be more likely to persuade me to part with $40, or what ever it is, if your online support was impeccably done, childishly easy to find the info I need quickly and get the debugger etc working with the minimal of fuss.

It seems to be that the properties page in the documentation had exactly the right and simple information that related to your configuration. The solution was clearly in the first part of the project properties documentation mentioned in my first response.