Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic re: debug upgrade installation (Read 7353 times)
Jim Brooks
Junior Member
**
Offline


Posts: 11
Location: Canada
Joined: Mar 2nd, 2013
re: debug upgrade installation
Mar 3rd, 2013 at 7:47pm
Print Post  
I must be having a slow day.
I have installed and run the visual studio and loaded a sample project(blink). Note when I installed the arduino extensions, the installer said I needed to remove and re-install it(not specific ms visual studio or arduino for visual studio) I did a removal-reinstall of MSVS and the arduino extensions but still got the warning. I tried running things and was able to open a project, build and upload but could not get breakpoints working. No debugger extension.
I downloaded and installed the debugger without error but don't see the additions shown in the yahoo video. What am I doing wrong? Is there an example of first time use for the debugger. I don't see the debugger properties as shown in the video.

Thanks for any help
Jim
Undecided
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: debug upgrade installation
Reply #1 - Mar 3rd, 2013 at 8:21pm
Print Post  
I don't know what the re-install was about. There is only one plugin and unlesss vs has not shutdown it will install without uninstall. I think that message was from some windows installer component and specific to you machine.

As for the debugger it sounds like you cant find the F4 project properties?
  
Back to top
IP Logged
 
Jim Brooks
Junior Member
**
Offline


Posts: 11
Location: Canada
Joined: Mar 2nd, 2013
Re: debug upgrade installation
Reply #2 - Mar 3rd, 2013 at 9:46pm
Print Post  
I read in one of the posts that if things didn't work right to remove and re-install arduino for VS.
I do see project properties at least I think that's what I'm looking at but debug refers to windows debug without the visual micro options
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: debug upgrade installation
Reply #3 - Mar 3rd, 2013 at 10:31pm
Print Post  
Hi Jim

Okay I think this post probably belongs in the debugger beta section because everything sounds like it is working okay, you just can't find the "Properties Window"

See if all this makes sense?

The uninstall message is the standard windows installer "Uninstall or Repair" message we see if we attempt to install software that is already installed? 

The debugger instructions say to first make sure the plugin is installed correctly by compiling a sketch such as the "Blink" example. I am assuming you have confirmed the compile is working and you have a list of Arduino boards and other user interface extensions for the standard non-debugging plugin?

If the standard plugin is working then the post you read about needing to uninstall before installing relates to people who have an install problem upgrading from one vm version to another will not be relevant.


The debugger installer does not alter the version of the standard plugin it simply adds some additional support files for the debugger. You said the install of the debugger update ran okay so that was all that was needed.

So it does seem that the only problem you have is to find the properties window. You are not alone in being confused finding this window, there are some other posts from users who have had the same problem for a couple of different reasons. So here is a summary of those posts ...

It is confusing in VS because there is a "Property Window", "Property Pages" and a "Property Manager". The plugin extends the "Property Window". The "Property Window" is a dock-able tool window which is why it is called a window (it does not look like a conventional on-top dialog window).

The "Property Window" is accessed by clicking the name of the project in the "Solution Explorer" and pressing F4. If that doesn't work then there should be a menu item at the top of the VS ide called "View>Property Window" or "View>Other Windows>Property Window". It does change slightly across VS versions.

When the "Property Window" is active you will see its contents change as you click/select different "files/folders/project names/solution name" in the solution tree.

One user had a problem seeing the properties window when F4 was pressed because the user had forgotten he had previously minimized the property window to a tab/button on the outer edge of the VS Ide. So if it doesn't appear look carefully at the Vs Ide for a tab called "Property Window"

FYI: The "Properties Pages" and "Property Manager" all relate to standard Microsoft Win32 C++ development which the plugin ignores and overrides. We override the intellisense system of VS C++ projects providing the Arduino sources instead of Win32. This is why you see options for windows debug etc. Ignore all of the options in these windows when in an Arduino projects. You can close these windows when working in an Arduino project.

  
Back to top
IP Logged
 
Jim Brooks
Junior Member
**
Offline


Posts: 11
Location: Canada
Joined: Mar 2nd, 2013
Re: debug upgrade installation
Reply #4 - Mar 3rd, 2013 at 11:08pm
Print Post  
Thanks Tim,

Almost there.
Debugger is working but... I wan't to step into library code(assuming it's not using timer 0 or serial port) and although I can get the code to pause, step into simply causes it to run again, not single step. Am I asking too much?

Re F4, I'm using a dell laptop and pressing F4 plus the fn key causes the output cursor to sequence between the debug output statements and the paused messages.
Jim

  
Back to top
 
IP Logged
 
Jim Brooks
Junior Member
**
Offline


Posts: 11
Location: Canada
Joined: Mar 2nd, 2013
Re: debug upgrade installation
Reply #5 - Mar 3rd, 2013 at 11:14pm
Print Post  
I noticed as well that the details for fields, at the bottom of the properties page is truncated. making the window wider helps but there are not sliders to allow you to see all the text so all the effort you put into detailing the fields is only partially available.
Overall though it is a very impressive job and something sorely needed to aid Arduino development.
Thanks so much for your help and patience in getting me running.
Jim
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: debug upgrade installation
Reply #6 - Mar 4th, 2013 at 12:25am
Print Post  
Good news. 

I know what you mean about the properties info/tip text. It's better if the properties window is docked full height but takes up too much room. Hopefully they will soon move to the Micro Explorer where I would like to consolidate a number of features. One place will be easier for all.

You can step but only between breakpoints at the moment and you can't debug libraries yet. 

Obviously you can perform higher level debug of libraries using public variables and expressions from any library that is available to a sketch source (ino,cpp,c)

To enable debug step you need to set the project property "Enable Break/Pause=True". Update of variables with {x=?} works with or without break/pause. The default is false because it is safer for some autonomous robots such as planes and copters.

When a breakpoint is hit you can use F5 or any of the "Debug>Start", "Step", "Run" options to jump to the next breakpoint.
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint