<p dir="auto">Since <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="468703548" data-permission-text="Title is private" data-url="https://github.com/microsoft/terminal/issues/1987" data-hovercard-type="issue" data-hovercard-url="/microsoft/terminal/issues/1987/hovercard" href="https://github.com/microsoft/terminal/issues/1987">#1987</a>, our SxS manifest is auto-generated, so it's certainly possible to run the terminal unpackaged again. However, we need the <code class="notranslate">resources.pri</code> that's only generated by building the CascadiaPackage project. Ideally, we'd be able to rebuild the terminal code (with <code class="notranslate">bx</code>, <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="475150143" data-permission-text="Title is private" data-url="https://github.com/microsoft/terminal/issues/2168" data-hovercard-type="pull_request" data-hovercard-url="/microsoft/terminal/pull/2168/hovercard" href="https://github.com/microsoft/terminal/pull/2168">#2168</a>), and launch it using <code class="notranslate">openterm</code>. We need to figure out a way to get openterm to build the appx's resources.pri for us, and not re-build every time <code class="notranslate">openterm</code> is called.</p>
<p dir="auto">I've built successful from command line using the following command.<br>
<code class="notranslate">msbuild /p:Configuration=Release /p:Platform=x64 /p:PlatformToolset=v142 /p:TargetPlatformVersion=10.0.18362.0 /p:PreferredToolArchitecture=x64 OpenConsole.sln</code><br>
I'm trying to find a possible solution for deploying from the command line. Is adding <code class="notranslate">/p:DeployOnBuild=true</code> enough? What other things need be done if necessary? Any guidance on what Deploy does, e.g. copying files to where, writing some environmental variables?</p>