Hi,

Deep search is simply a way to discover libraries from non-ino project code and other libraries. It's a recent addition to the ide which does it by default and can't be disabled. It is optional in visual micro because the old way of adding #includes for each library to the .ino source still works and can improve compile times.

If you are a Pro user and you will find the "vmicro->add code" menu there is an option to add/create a new library. Click it and create a test library. 

Notice the location where it is created, for example "project\src\_micro-api\libraries". Libraries located below this sub folder structure of any project become "local" project libraries. 

Local libraries override the versions in the standard Arduino locations (if they exist). 

Local libraries should be included in the project source code in the exact same way as if they existed in the standard arduino library locations (ie: without path qualifiers), This ensures a local library can become a shared standard arduino library without code change.

You can copy existing libraries and to the correct location below the project then use the "show all files" view of the solution explorer, right click and include the library sources into the current project. As stated above, as long as the are in the designated location they won't be compiled with the project sources and will be compiled as libraries.

Maybe some interesting things in my answer about a new shared project code facility that is about to be released here here http://www.visualmicro.com/forums/YaBB.pl?num=1482999947

Quote:


This is entirely up to you. If you have not used the special features of visual micro such as compiler defines, debug settings etc. and only want to store the basics then an Arduino project is simply the code in the folder and sub folders. Visual Micro can read that code and create a working arduino project from it because this is how the arduino ide works.

If you use the visual studio solution explorer to add/remove certain sources from the project folder or sub folders then you need the .vcxproj and vcxfilter files

The solution (.sln) stores a list of project locations for the current solution. It's just a handy way to work to have a solution to open so it's up to you if you store it. The only other thing a solution stores is breakpoints for the debugger.

The __vm folder below a sketch stores the setting such as configuration specific compiler defines, debug settings etc (project properties), last build info and other non-code settings, It's up to you if you want to share this. Visual Micro will recreate any settings files it can't find.

The build output is copied to the debug/release (configuration name) folders. It's up to you if you need to keep these in source control.

All the visual studio and visual micro settings files are simple text files (normally .xml) and can be viewed with a text editor if unsure what they contain.