Agreed thanks. It's being worked on but do please say if you are encountering long compile times. 

Normally the compile should be less than a few seconds. 

If you are using libraries that contain many files then switching off "visual micro>deep search includes" can produce significant performance increase.

It's a difficult one.

It is the default/forced in the arduino ide since 1.6.6 and can not be disabled....

New users always hit problems when a library also requires another library. Most common is spi.h and wire.h. 

The feature automatically finds these hidden relationships and #includes them but more experienced users can simply added them to the project_name.ino and then the feature has no purpose.

So, either new users get compile errors or more experienced users find it slow. 

However most important is that new users don't give Visual Micro a bad review because something works in Arduino and not in Visual Micro.

I put a big link at the top of the visualmicro.com home page about this and am considering how else to tell people. 

Hopefully you can now understand the dilemma