Resolution

To fix this issue, make sure you:

1. Run the command from the location of the EXE (Cloudhouse.Container.Deployment.exe which is in the root of your Container in this example).
2. Add the relative path command ".\" to the beginning of your command. For example:

.\Cloudhouse.Container.Deployment.exe --deploydir c:\temp --accepteula

If you still encounter problems, please contact your Cloudhouse Partner in the first instance (if relevant), otherwise contact Cloudhouse Support for further assistance.

Symptoms

When deploying an Application Compatibility Package/Container, I receive the following error:

Cloudhouse.Container.Deployment.exe -- Cloudhouse.Container.Deployment.exe : The term
'Cloudhouse.Container.Deployment.exe' is not recognized as the name
of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is 
correct and try again.
At line:1 char:1
+ Cloudhouse.Container.Deployment.exe --deploydir c:\temp --accepteula
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Cloudhouse.Container.Deploym
   ent.exe:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command Cloudhouse.Container.Deployment.exe was not
found, but does exist in the current location. Windows PowerShell
does not load commands from the current location by default. If you trust this command, instead type:
".\Cloudhouse.Container.Deployment.exe". See "get-help
about_Command_Precedence" for more details.

Cause

As mentioned in the "Suggestion" part of this error, the reason you see this error is because by default Windows PowerShell does not load commands from the current location.