[Issue 18641] VisualD - First 5 minutes - Improve experience adding .d files to existing C++ projects

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=18641

--- Comment #2 from Manu <turkeyman at gmail.com> ---
Why don't we just amend the global C/C++ props and include the D lib paths the
same as MS does for CRT paths? I don't think anyone will mind ;)

The link comment thing is interesting. Why only in main? MSC definitely
includes the runtime lib reference in every single .obj file it emits (unless
compiling with /Zl). I feel like we should do the same thing.
Have you had experience where the linker ignores it?


> With static libraries this gets a bit more complicated as these settings must be propagated to the actual link step in a different project.

What does MSC do?
I feel like we should probably just match MSC's patterns verbatim, with respect
to link paths, embedding library references, etc.

--