Bugfix VS project template

[hiroMTB]

Try to solve two issues.

• Issue 1. mismatch detected for '_ITERATOR_DEBUG_LEVEL'
• Issue 2. Update vs template for when multiple addons with identical class names are used.
  -> This is not solved by this PR but see comment Bugfix VS project template #6122 (comment).

With this PR's initial commit, Issue 1 has been solved. But Issue 2 still remains.

There are several output files should be placed inside of an intermediate file folder.
For example,

• *.tlog folder
• .log file
• icon.rc file

And these changes should be tested on VS2018 and VS2015.

• VS2017
• VS2015 seems like oF0.10.0 is not compatible

More commits coming later.

Official documents about VS build macro
https://docs.microsoft.com/en-us/cpp/ide/common-macros-for-build-commands-and-properties?view=vs-2017

[hiroMTB]

For reference, cinder is using following setup for Intermediate Directory (which can be used as $(IntDir) )
$(ProjectDir)build\$(Platform)\$(Configuration)\intermediate\

oF's Intermediate Directory is
obj\$(Configuration)\

[arturoc]

thanks!

[hiroMTB]

Thanks @arturoc
But I have one more commit must be added.
I already pushed but it doesn't appear here.
Here is a commit to my oF fork.
hiroMTB@9a6f4b9

Please feel free to commit directly if it's easier. ;-)

[hiroMTB]

And couldn't find a general solution for issue 2.
but instead of changing oF itself, we can avoid this issue by setting a unique object file name to one of conflicting file.

Let's say we have addonA and addonB and both has MyFile.cpp.

1. Open your VS project and right click MyFile.cpp file in solution explorer.
2. Go to Properties -> C/C++ -> Output Files -> Object file name
3. Change $(IntDir) to $(IntDir)/MyFile_from_addonB
4. compile

This way, vs generates MyFile_from_addonB.obj under /obj folder.