Hello, I have  problem with IntelliSense in VisualStudio.

It shows me 78 Errors and underlines text in the code. However the code is compilable without compiler errors. The PrintScreen is attached.

The error list can be toggled to "Build only" so the messages don't take space in error list but the underlines persist.

Can you please give me a advice how to remove this behavior? (If it's possible... )

I'm using Visual Studio Community 2015 with Visual Micro version: 1604.18.0

Hi,

Sorry for the delay. 

The different Visual Studio versions have handled intellisense in different ways and it looks like the sam/due definitions should be reviewed.

Q: Can you provide a sketch for testing and I can take a look at it?

info ..

Atmel studio is slightly better for gcc intellisense, some of the reason is that it ignores more things that it doesn't understand than Vs. Microsoft are also working on adding better support for gcc instead of normal vc++.

Hopefully we can make a big improvement but if the issues persists and atmel fix a few things there will certainly be updated atmel studio versions again.

Maybe a solution. Microsoft released Clang compatibility in VS2015 Update 1

I tried using a new Visual Studio project type of Andoid/clang/gcc and the intellisense errors were almost none. No errors when working with "Open Documents" mode (see image).

During the next few weeks/month I will look into using the new VS clang without the Android stuff and instead of the standard Microsoft C++ project type we currently use.

You try it if you want. The android for visual studio system uses C++ projects so Visual Micro should work okay. 

The Android tools for VS are required (free) and can be installed via control panel>add or remove programs>visual studio>change.

Then you can use File>New>Project>Cross Platform>Static Library (Android) to create a project. You can remove any files that are automatically added to the new project. Then add a .ino of the same name and you have an Arduino project. 

In your version of Visual Micro you might need to restart the ide after adding the .ino to a project that was not previously an arduino project. (You don't need to do that in the next release)

You can copy and rename the .vcxproj if you want to use it in an existing standard visual micro project.

When moving files around remember these rules if you want visual micro to see a c++ project as an arduino project:-

• A project (vcxproj) must be in a folder of the same name
• The project must contain a .ino of the same name (in the same folder)

Notice that I have changed the "Platform Toolset" to GCC in the project properties. 

All other project properties can be ignored but you can alter most properties except for macros and include paths which Visual Micro maintains. 

After you have the correct .vcxproj type you should find gcc intellisense works much better.

Tim@Visual Micro wrote on Apr 25^th, 2016 at 11:48pm:


Hello!

I wanted to try Your solution, but I stucked on the first point: installing Android tools... 

There are plenty of Android tools in the menu. Whitch one is the needed one?

I installed those 2 tools and created a new project as You described. Then I copied and renamed the source files and IntelliSense seems OK. However another problem appeared. It seems that VS doesn't recognize arduino file properly and I'm not able to compile the project.

Buttons "Build" and "Built and Upload" are disabled and when I try to build by "Debug>Start Debugging", it shows error.

I've also changed the Platform Toolset to GCC 4.9.

Hi,

Thanks for the update. I will look into the errors with the new system. 

I think I found the answer to the intellisense errors with the Clang project. I switched the tool bar platform from x86 to ARM and some remaining errors disappeared.


ps:
When time allows, if you can replicate a small example with a standard project, zip the entire project folder and email info[at]visualmicro.com with it sometime that would be appreciated.

There have been some intellisense improvements for the Due for the next release of visual micro. 

I think it will make a huge difference (but still won't be perfect).

It was caused by the intellisense revamp in the latest release and applied to all avr boards

An update has just been published with a fix 1606.8

Thanks for the report.