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
Hot Topic (More than 8 Replies) Teensy EEPROM intellisense error - "Input string was not in a correct format" (solved) (Read 8343 times)
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Teensy EEPROM intellisense error - "Input string was not in a correct format" (solved)
Jun 3rd, 2016 at 5:26pm
Print Post  
Like the title says, I'm trying to go from 1605.14.0 to 1605.28.0  and I get an error that says it was unable to install the extension to all the selected products because:
"Input string was not in a correct format"

I've attached the install log.  It seems like it's out of my hands, push another update soon?

Thanks!  Smiley
« Last Edit: Jun 9th, 2016 at 3:06pm by Tim@Visual Micro »  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #1 - Jun 3rd, 2016 at 5:52pm
Print Post  
Hi,

This is a microsoft vsix installer error. The version string format has not altered and many others have installed with issue. So I am a bit confused.

Can you please give details of op sys ver and visual studio version. Also open visual studio help>about and give screen shot.

Thanks very much.
  
Back to top
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #2 - Jun 3rd, 2016 at 6:18pm
Print Post  
I was afraid of that when I couldn't find anyone else having the same problem.

I attached the visual studio help>about and the My Computer>Properties view.  (64 bit Win 7)

I'm trying to upgrade VisualMicro because I've been having issues with red underlines where they don't belong, despite compiling OK.  I expect this update to fix that, but I figured I should mention it
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #3 - Jun 3rd, 2016 at 6:27pm
Print Post  
Also, I have tried running it as admin and downloading the installer from outside VS.  We get updates pushed from IT so I'm going around them and updating windows, I'll let you know if that works.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #4 - Jun 3rd, 2016 at 6:28pm
Print Post  
Which board and arduino ide version are you using?
  
Back to top
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #5 - Jun 3rd, 2016 at 6:35pm
Print Post  
Teensy 3.1 and Arduino 1.6.8
  
Back to top
 
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #6 - Jun 3rd, 2016 at 6:48pm
Print Post  
Still failed the same way after updates
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #7 - Jun 3rd, 2016 at 6:55pm
Print Post  
1) Can you give me some sample code that compiles but has red underlines?

2) If you create a new empty project and click "View>Errors List". How many errors show?

Thanks
  
Back to top
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #8 - Jun 3rd, 2016 at 7:32pm
Print Post  
Ok, I've done all that and attached two projects and some screenshots in a zip.
The empty project didn't have any errors.

When I have my include in the INO file then the #include part is ok but the object gets underlined

When I have an include in a .H file then both the #include and the object's use in the .CPP are underlined

I had deep search on.  If I turn it off it will no longer compile until I change the SPI include to #include <SPI\SPI.h>  Then all the SPI underlining disappears.  Changing the eeprom include to #include <EEPROM\EEPROM.h> removes the EEPROM underlining too, although it still isn't necessary for it to compile.
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #9 - Jun 3rd, 2016 at 7:34pm
Print Post  
pictures
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Mat
Junior Member
**
Offline


Posts: 10
Joined: Dec 22nd, 2015
Re: Can't update from 1605.14.0 to 1605.28.0 "Input string was not in a correct format"
Reply #10 - Jun 3rd, 2016 at 7:35pm
Print Post  
pics 2/2
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Teensy EEPROM intellisense error - "Input string was not in a correct format"
Reply #11 - Jun 3rd, 2016 at 8:29pm
Print Post  
Thanks that's useful.

1)

I found an intellisense bug with the EEprom where the include paths are in the wrong order. In the case of teensy it has an eeprom.h in its core which is cancelling out the intellisense for the EEPROM library. Compile is OK.

Fixed in next release

2)

The SPI.h intellisense issue is because you have not #included the spi.h in the project_name.ino. This is what deep search does, it finds library #includes in cpp files and in other libraries. 

Recently arduino changed the way library paths can be discovered. In visual micro this is optional (because it's slow) and called "deep search includes".

Previously (or with deep search off) #includes had to be added into the project_name.ino. This is the fastest way for visual micro to determine which libraries are required.

However "deep search" is very slow so has not yet been implemented for intellisense, only for compile. This is because it needs some additional caching work to avoid long delays when editing code.

So simply add #include <spi.h> to the project_name.ino and intellisense will work for spi but also compile will work with "deep search" switched off.
« Last Edit: Jun 9th, 2016 at 3:06pm by Tim@Visual Micro »  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint