Best practise for _MSC_VER macro

I found a very old thread on this topic but I wonder if the approach is up-to-date since the compiler used by CVI has changed since version 2013.

Which is the best practise to use when compiling with CVI 2017 sources which use Windows SDK files?

Should be _MSC_VER macro defined to some value?

Or should it be left undefined?

I'm interested in a general solution from NI engeneers.

Thanks