Why bother with dotnet build before dotnet publish? : <p>Welp.  This seems like the type of question where I'll facepalm seeing the answer.</p>

<p>So...</p>

<p>Why bother with <code>dotnet build</code> before doing a <code>dotnet publish</code>?</p>

<p><code>build</code> automatically does a <code>restore</code>.  Cool.  </p>

<p>It seems <code>publish</code> does a <code>build</code> (unless you tell it not to).  So... Why bother doing the build if you're going to publish right after?  Why not just publish and everything happens in one step?</p>

<p>For further clarity... </p>

<p>I am asking in a basic scenario like:</p>

<ul>
<li><code>dotnet build -c Release MyProj</code></li>
<li><code>dotnet publish -c Release -o /somedir MyProj</code></li>
</ul>

<p>versus just</p>

<ul>
<li><code>dotnet publish -c Release -o /somedir MyProj</code></li>
</ul>

<p>They seem to do the same thing.</p>
