The issue is that I get no error, but I get a loading screen showing what appears to be PowerShell successfully called, but everything is suspended (no failures, it just lingers with Windows PowerShell [copyright info]. In digging around, I decided to just see if I could get it to write out a warning and it appears that it is setting the execution policy to unrestricted (which is how my system is currently set as well).
I did think that maybe the execution policy wasn't set to unrestricted, so I tried passing in the -Force parameter, but got an error about it being invalid.
The PS script:
Write-Warning "Called successfully.
The XML code to call it:
<Target Name="DoSomething">
<PropertyGroup>
<ponyone>FullOne</ponyone>
<ponytwo>HalfOne</ponytwo>
<ponytree>LatterExcen</ponytree>
</PropertyGroup>
<Exec Command="powershell.exe -NonInteractive -executionpolicy Unrestricted" />
<Exec Command="powershell.exe .\Do-Something.ps1 FullOne HalfOne LatterExcen" />
</Target>
Confirmed that this is because of the executionpolicy; when I only run the second script, it errors due to scripts being disabled, even though PowerShell shows the execution policy is unrestricted.