Why is this header being included?

Often I'll find a visual studio project not compiling as a header file generates an error. Then I realise there's no need for that header to be needed as it's totally unrelated.
So why is it being included?
It can take a lot of guesswork to track down the reason in a large project, but here's a quick method of showing the whole header tree for a cpp.

Add "/ShowIncludes" to the command line options for that cpp. A recursive list is displayed of each included file. Hopefully an unnecessary header file can be identified to enable this tree to be pruned.

Alternatively set the compile option:
http://msdn.microsoft.com/en-us/library/hdkef6tk(v=vs.80).aspx

Vijay World: P4EXP Windows Explorer Integration - Problem Solve...

Vijay World: P4EXP Windows Explorer Integration - Problem Solve...: There were lots of issues  and i was struggling to use p4exp which come in bundle with p4v setup. i Couldn't configure it properly for a...

I forget this one every time when installing perforce explorer integration. Duh.

Subst drives only visible to some applications?

Well this had me stumped for a while. I have a Z drive mapped to a folder on C using VisualSubst.

Yet some applications would deny that the Z drive existed. Very odd.

Finally it dawned on me - the applications which could not see Z were running as administrator.

The solution? Run VisualSubst again, this time as administrator and the drive mapping will not be listed.. add it here and voilá. All applications can now see your mapped drive letter.

--


For a better solution, see http://en.wikipedia.org/wiki/SUBST#Method_3