Hi,

You have to use the structure published by arduino.cc. An arduino project can only have code in an \src sub folder or any folder below that.

So in your case that would mean moving the components to be src\components

There are other options for shared code from other locations and arduino libraries but best to avoid until you have a clear understanding of what can be done within the arduino standard. 

There is also option to set compiler -I include path for project or solution but the compiler include paths would not cause code in the included folders to be compiled.

All of the VS property page options except for intermediate and final build paths should be treated as readonly so that we can force VS intellisense to work. When a build happens the project properties are not used because they don't make a lot of sense for arduino. Visual micro handles the build and leaves vs to manage the intellisense after feeding it paths.

We are considering extending visual micro to give you simple paths to add to a config file that allows external code to be included but it will probably cause more complications than what it would solve. The point that people miss is that for multiple .ino files to be supported they are actually combined into a .cpp in background when the build happens. That means we have to build in a hidden temp folder which blows the concept of allowing people to include other sources simply because noone would ever know what the #include <relative path?> would be.

As I have said there are options for external code in terms of shared code projects or arduino compatible libraries but you do need to fully understand the way arduino works before using those options.

The simplest solution is to work from the \src sub folder of your project and then all your #includes will be relative and obvious. It is also supported to put the .ino files in the \src folder instead of the project folder, in this case your #includes (from .ino to components sub folder) would avoid needing \src\ and would be as you already have them.

I hope this helps

Arduino supports \src below each sketch. This means each project can have \src folder with sub folders below it. This has no relation to libraries.

If you click File>New>Project you will see there is an empty Visual Micro project with the \src folder included for you along with a readme file that explains how arduino works with sub folders.

As I said the c++ vs properties are managed by visual micro. You can not change them to any useful effect.

You can click a project name and press F4 then see the compile flags where you can add -I includes however I think you should keep things arduino compatible

Your include example below #include "FT_Platform.h" is not shown in the source code image so it's hard to give you help. I can tell you that the project path is set as a compiler include by both the arduino ide and visual micro. So your .ino code can reference #include "src/ftdi/FT_Eve_Hal/Hdr/FT_Platform.h"

note there is a bug fix around #includes with relative paths available from the 1908.7 work in progress here https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Yes if you want to stay arduino compatible which is recommended because it avoids confusion.

Thanks for the update.

A non-arduino compatible way to add your includes might be to click "vMicro>Project Properties" and add the following as a compiler>extra flags:-

-I"{sketch_path}/src/..../hdr" 

note: {sketch_path} is a build variable. You can see all the build variables in the verbose output when "show build properties" is enabled.

Then hopefully both intellisense and the compiler will be happy with 

#include <FT_Platform.h> 

Great thanks for the update, yes I agree. Staying within the Arduino framework is the best solution.