Start-ASConversion
Edition:Powershell cmdlets are enabled with AdminStudio Enterprise Edition and with Workflow Manager.
Use the Start-ASConversion cmdlet to start Automatic Application Converter using a given .aacx file. This cmdlet is usually used after you have added one or more packages using the Add-ASPackageForConversion cmdlet, which returns a path to an .aacx file. This .aacx file is then passed to the Start-ASConversion cmdlet to start the conversion.
Examples
The following are examples of how to use the Start-ASConversion cmdlet:
Start-ASConversion-AACSettings "C:\Personal\AAC\test.aacx" -BuildMSI
Start-ASConversion-AACSettings "C:\Personal\AAC\test.aacx"-OutputPath "C:\Result"-BuildAppV‑BuildXenApp-BuildSymantec-BuildThinApp -BuildMSI
Parameters
The Start-ASConversion cmdlet has the following parameters:
Parameter |
Description |
AACSettings |
The Automated Application Converter project file to use for Conversion. Use to specify the Automated Application Converter project file to use during conversion. If it is not supplied, a copy of the project file specified in the platform settings file will be used. |
[VMPlatform] |
Specify platform to use for automated repackaging, such as 600Sx64, 501, or 502S. |
[OutputPath] |
Output folder under which all output will be collected. |
[BuildAppV] |
Specify this parameter to build App-V packages. |
[BuildXenApp] |
Specify this parameter to build Citrix XenApp profiles. |
[BuildThinApp] |
Specify this parameter to build VMWare ThinApp packages. |
[BuildMSI] |
Specify this parameter to build Windows Installer packages. |
Return Values
The path to an .aacx file is returned.