Hi,

As far as #defines in code is concerned it's just down to the arduino/gcc/c++ rules and Visual Micro has no control over that. I thought people do put global #defines in files but often via an #include "myheader.h" or some other header file.

You can also add your own defines in the visual micro project properties either for all configurations and/or per configuration (ie: different between release and debug configurations) 

The project property version are carried through all compiler commands so can be used to affect code outside of the project code such as libraries.

The documentation on visualmicro.com shows some facilities/User-Guide.aspx?doc=Project-Defines.html

If I recall you can ; separate one=1;two=2

or you can add them to the compiler flags, again in the same project properties as the defines. In that case they will be defined like this:-

-Done=1 -Dtwo=2

The vMicro>Compiler>Verbose option can be used to see what defines are currently being used by the compiler.

Final thought

The nice thing about putting them in code is that your code will still work in the Arduino IDE