You can't debug them from documents\arduino\libraries yet but you can place them in a special location so that they continue to work as libraries but can be debugged.

If you right click the project in the solution explorer you will see "Add>New Arduino Library". This will create an example library in "project\src\micro libraries\[new lib name]"

Visual micro allows for this special libraries folder structure below the project. Libraries placed in the special location will override the published versions in "documents\arduino\libraries" and can be debugged. The location is treated as an official arduino libraries location so that #includes can remain as "LibName.h" without path specification.

Is "Visual Micro\Deep search includes" Off?

If you use a version 2 arduino library format you will need a library.properties in the root of the library

Does creating a new library using the visual micro menus work in a new simple project?

Thanks

I just published a new build that allows the "Visual Micro\Deep search includes" to work with local libraries.

If that is not (or was not) the problem then it sounds like your "tools>options>visual micro>compatibility settings" might be wrong. Please let me know if they are all enabled/true?

Can't see the output please email it.

The compiler uses the project to work out which files to include

It might also be an idea to zip and email your project with folders and files.

Thanks

You can always email the zip. It's easier to delete old files that way otherwise the forum fills up.

I am sorry if I have not been clear previously when I stressed the importance of using the "Show all files" solution explorer view. 

The "show all files view" avoids a lot of confusion and allows you to clearly see what you have (or have not included)  included in your project.

It is very confusing to work in Visual Studio with deeply nested folders without having this view enabled.

I think you should use the visual studio solution in the way I show below instead of using windows explorer in the way you have shown in your post. The windows explorer view does not give you any indication of what is included in your project so does not show what will be compiled.

Below is what I could see when I opened the project that you attached.

note: Historically all files in the root of an arduino project are compiled because this is what the arduino ide does. This is also the default behavior for visual micro. However source code in sub folders is only compiled if it is included in the visual studio project and this applies to library sources. (local libraries are a relatively new feature and up for discussion if its confusing)

If I move the libraries from the Arduino/Rover/src... folder back to the Arduini/Libraries folder, the errors all go away. There is something very wonky about how the compiler deals with the libraries when they are included directly.

Bob

Tim,

Yes to both questions. I have since moved all the libraries back to the Arduino/libraries folder but I can move them back to the Rover folder easily and run the tests again if that will help. Having done this a few times already, it is getting easier to do. 

I still think that there are enough questions that a Skype session would be the most efficient way of resolving them.

Bob

Thanks, Tim and I fully appreciate the time you have spend and vs. the revenue received. I did (just) manage to get the code and am now testing to see if I can get debug to work in the libraries. 

Going forward, I do want to support your great effort. Seldom in my 48 years as a software developer (see rhj4.com blog) have I encountered the level of responsiveness I have experienced with you. I will gladly write a testimonial if that will help your marketing efforts.

As far as Skype (or Zoom...) time, I am comfortable paying you for that time if I can afford your rate. Let me know what it would cost me.

Thanks,

Bob