Hi,

1)

If you ensure you have the "pragma once" command at the top of your header files I hope you only see one mesage

2)

To answer the question I suggest asking on the arduino.cc web site. I wouldn't mention your lib is in _micro-api because that will confuse. It's just a standard arduino library.

3)

A tip for less confusion is to put your libraries in a folder outside of the project folder. Maybe a sibling folder of the project, both below the solution.

Putting libs below the _micro-api\librares folder and also making them shared projects kind of defeats the object of shared lib projects because files under the _micro-api can be directly included into the project via the solution explorer but isn't very compatible with the arduino ide.

- Solution
     -  MyLibs
        -  Lib1
     -  MyProject1

Hope this helps a bit.

Hi,

Source defines affect libraries is related to cache/build and unrelated to passing defines to the library compiler. I would leave that option at the default setting and then ignore it.

In the arduino world project defines do not affect libraries which is why visual micro has the additional project property option.

Maybe a work around is to create a library called "MyDefinesLib" (or some other name) that includes the defines in MyDefinesLib.h and then reference the lib header <MyDefinesLib.h> in all libraries and the project.

Does that work?

Quote:

Yes it's a tricky area. I think that feature was added long ago for the ArduPilot drone project that had a modified ide. Probably needs to be removed because normal arduino doesn't work that way.

Quote:


I can look at this if needed but it is an area that can be confusing due to the way VS works. There is a mini button above the solution explorer that auto synchronizes the solution explorer with the active code that is being edited. If that option is off (which is how I prefer to work) then the active code and the solution explorer are two different selections.

You might think that clicking the solution explorer should always be the selected project or vica versa. However if you look at the Project, Build and Debug menu you will see which project VS thinks is active. It's not always the one you would think should be active. 

Then when you press F5 to upload which project is uploaded? The one being edited or the one selected in the solution explorer.

Maybe the bug is that the project properties are not refreshing correctly.

Which version of VS are you using exactly? 

Quote:


Yes its on the list. Time is short and Microsoft/Arduino in VsCode with the linux, mac and some windows users are taking all the blogs and pr so i'm spending more of the available time considering marketing at the moment. I don't think windows/vs users like blogging or tweeting much

Quote:


There are defines required to make vs intellisense work which would interfere with the build (because the real compiler sets what it wants accurately). Therefore the standard vs project defines need to be automatically updated with "stuff" that makes intellisense work.

Global defines are stored in a section of the project or .user file. We use global project properties but you have to use the project properties for now. If you put it at the bottom of the screen it can take the full length so is easier to work with. 

Defines for the configuration are stored in the xml files in the \_vm folder. You will see the file names contain the project name and the configuration name. However because vs sends messages to show the project properties many times the files are cached. There is only one cache for all projects in a solution, so clicking between two top level projects should invalidate it. 

Quote:


The site is in the process of being re-done with a new better documentation/wiki area. Will add to that but there are only the config specific files I have mentioned and properties in the proj.