On the vMicro>Compiler menu warnings can be enabled/disabled for three groups of files Project, Libraries, Core.

It is no currently possible to configure warning level for a specific file. It might be possible to enable/disable warning in code using a #pragma statement. It would be important to ensure you look at gcc documentation and not visual studio VC++ for that.

It's a good idea and should be quite easy to implement, we will add it to the list and next release if time allows.

That is fine take all the time you want.   

One day with visual micro was enough for me to learn that is it not the tool I need to be using.   

Basically I got a Visual Micro project from a customer.  They want to go to production of product using code. 

Visual Micro is no something you want to use for production as it abstracts much of the build process and settings.  Which is what Arduino and Visual Micro was designed to do.   So it is not about what is missing, but rather the use case. 

To keep it very simple, if I can not script visual micro such that I run the build on a CI system like TravisCI. Then I feel it should not be used for commercial applications.   

Now if you basically export a makefile, nijia, cmake build system then it might be useful.  However again that is not your market segment.   

As such I will need to take this project and converting it to a more traditional build system.  At which point VSCode or other editors/IDEs can be used, and it works with TravisCI.

ps: the verbose build commands that visual micro shows are each an external process. You can tweak the warnings or other params and then run then in a cmd.exe prompt. Same end result just a little more cumbersome for repeated use.

It's only a pig from your perspective, there is a huge Arduino community and many commercial projects, many more prototypes for commercial. 

For an advanced programmer Arduino is certainly too simple but for a "maker" it's perfect. Minimum learning curve, simple installation, easy to support, well tried and tested open source libraries and examples. Rapid developement makes commercial sense too.

If you do decide to teak the build params for a file using the verbose output suggested earlier you can also re-link if need be. If you reporduce the output files then you can use "vMicro>Uploader>Upload Last Build" to upload. That will avoid your custom build from being destroyed by a new build prior to upload.