Why do we use `#include "stdafx.h"` instead of `#include <stdafx.h>`?
<p>From <a href="https://stackoverflow.com/a/21594/1245120">here</a>, it is said that:  </p>

<blockquote>
  <p>For <code>#include "filename"</code> the preprocessor searches in the same
  directory as the file containing the directive. This method is
  normally used to include programmer-defined header files.</p>
  
  <p>For <code>#include &lt;filename&gt;</code> the preprocessor searches in an implementation
  dependent manner, normally in search directories pre-designated by the
  compiler/IDE. This method is normally used to include standard library
  header files.  </p>
</blockquote>

<p>While <a href="https://en.wikipedia.org/wiki/Precompiled_header#stdafx.h" rel="nofollow noreferrer">this wiki link</a> suggests that <code>stdafx.h</code> is an header file pre-designed by <code>visual studio IDE</code>  </p>

<blockquote>
  <p>stdafx.h is a file, generated by Microsoft Visual Studio IDE wizards,
  that describes both standard system and project specific include files
  that are used frequently but hardly ever change.</p>
  
  <p>Compatible compilers (for example, Visual C++ 6.0 and newer) will
  precompile this file to reduce overall compile times. Visual C++ will
  not compile anything before the #include "stdafx.h" in the source
  file, unless the compile option /Yu'stdafx.h' is unchecked (by
  default); it assumes all code in the source up to and including that
  line is already compiled.</p>
  
  <p>The AFX in stdafx.h stands for Application Framework eXtensions. AFX
  was the original abbreviation for the Microsoft Foundation Classes
  (MFC). While the name stdafx.h is used by default, projects may
  specify an alternative name.  </p>
</blockquote>

<p>Then  </p>

<p><strong>Why do we use #include <code>"stdafx.h"</code> instead of <code>#include &lt;stdafx.h&gt;</code> ?</strong></p>