May 7th, 2025 at 10:30pm (UTC)
 
 

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
 
  VS Arduino › › › Visual Studio debug vs. release code
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Visual Studio debug vs. release code (Read 2944 times)
arduinoUser2
Junior Member
**
Offline


Posts: 41
Joined: Dec 30th, 2015
Visual Studio debug vs. release code
Nov 8th, 2017 at 5:53pm
Print Post  
Using Visual Studio Community 2017.
Board: HiLetgo ESP8266 NodeMCU LUA CP2102 ESP-12E

I am finding that release versions of the code works all the time, but the debug version works only rarely.

I looked and searched for information on this, but nothing I found was germane.

Is there some setting or procedure I am missing?
  
Back to top
 
IP Logged
 
arduinoUser2
Junior Member
**
Offline


Posts: 41
Joined: Dec 30th, 2015
Re: Visual Studio debug vs. release code
Reply #1 - Nov 9th, 2017 at 5:06pm
Print Post  
OK, Uncle!  For other than Americans, that means "I give up!"

I really want to use the debugging features of VS combined with Visual Micro IDE, but it just does not work reliably.  In thinking back on it, I have had this same problem when working with the Arduino UNO, but I did not realize it at the time.

I will still use the VS/VM IDE combination since the editor is nicer than the straight Arduino IDE.  I am sorely disappointed at this turn of events.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Visual Studio debug vs. release code
Reply #2 - Nov 10th, 2017 at 6:19am
Print Post  
Hi,

Please give more info when you post. You have a board that is capable of multiple types of upload so debug with serial might need to be configured slightly differently which is done with the menus.

It might also be useful to zip and email your _vm sub folder so I can see how many breakpoints and what settings are being used.

Thanks
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
arduinoUser2
Junior Member
**
Offline


Posts: 41
Joined: Dec 30th, 2015
Re: Visual Studio debug vs. release code
Reply #3 - Nov 10th, 2017 at 3:42pm
Print Post  
Tim,

This is related to my post of a few minutes ago at http://www.visualmicro.com/forums/YaBB.pl?num=1510070437/4#5.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Visual Studio debug vs. release code
Reply #4 - Nov 10th, 2017 at 4:20pm
Print Post  
I have another report. It might be that the short delay() visual micro normally uses when debug starts is being applied to the esp boards. It's not supposed to be due to an esp bug.

try this in your esp code to see the problem, use Release mode:-

Code
Select All
void setup()
{
  delay(2000);

  //now try to connect to the network with the esp. it will probably fail
}



Because of this issue visual micro is supposed to make an exception for esp boards by NOT adding a delay. Sounds like a  vsiual micro bug is adding the delay.

I will look into that
« Last Edit: Nov 10th, 2017 at 4:22pm by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

VS Arduino » Powered by YaBB 2.6.12!
YaBB Forum Software © 2000-2025. All Rights Reserved.