---

This section details on the original issue you should resolve

<issue_title>Convert all DotnetCommand tests that call "new" to DotnetNewCommand</issue_title>
<issue_description>We constantly see issues where the new command failes and needs to use the ephemeral hive. We should try to catch this in the dotnetcommand constructor and fail (if args[0] == "new") and convert all existing tests over so that we can enforce the ephemeral hives.</issue_description>

<agent_instructions>Look for tests that call DotnetCommand and do a new operation in that command. Likely they explicitly call out to the ephemeral hive. Try to move these tests over to use the DotnetNewCommand implementation instead. It should be very simple.

Example:

•            new DotnetCommand(_log, "new", "console", "-o", path, "-n", "myconsole").Execute().Should().Pass();
  

becomes

•             new DotnetNewCommand(_log, "console", "-o", path, "-n", "myconsole").Execute().Should().Pass();
  

if it has ephermeral hive, you can use WithVirtualHive()
</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@marcpopMSFT No rush on this but I thought this could be the next test update you do now that most tests are upgraded to the current target framework. Let me know if you have questions.